From: "menon.nishanth@gmail.com" <menon.nishanth@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: lots of inaccurate references to "FileName: include/asm-arm ..."
Date: Tue, 4 Dec 2012 13:08:55 -0600 [thread overview]
Message-ID: <CAGo_u6q97PTW+FAUnTOw1h-Jx=ZbO_hqqfAyP-d8_7DkVZEnkQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212041048580.29673@oneiric>
On Tue, Dec 4, 2012 at 10:13 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> while roaming around in the arm/omap files, i noticed that numerous
> files have obsolete "FileName:" values, given that stuff that was once
> in "include/asm-arm" has clearly moved, so you find header files like
> arch/arm/mach-omap/include/mach/gpmc_nand.h that contain:
>
> * FileName: include/asm-arm/arch-omap/gpmc_nand.h
> *
> * OMAP's General Purpose Memory Controller (GPMC) has a NAND controller
> * embedded. this file provides the platform data structure required to
> * hook on to it.
> *
> */
> /*
> * (C) Copyright 2008
> * Texas Instruments, <www.ti.com>
> * Nishanth Menon <x0nishan@ti.com>
> *
> * Originally from Linux kernel:
> * http://linux.omap.com/pub/kernel/3430zoom/linux-ldp-v1.3.tar.gz
> * include/asm-arm/arch-omap/nand.h
>
> so the later comment as to the *origin* of the file is fine, but the
> earlier "FileName" value is obviously incorrect. does that matter?
> is that value used for any sort of documentation processing?
At least when I created the original file in 2008, I think it was
originally from
http://linux.omap.com/pub/kernel/3430zoom/
and the file there was include/asm-arm/arch-omap/nand.h
> p.s. you can see the number of these with a simple:
>
> $ grep -r "include/asm-arm" *
>
> since i'm working with a number of the ARM files, i'd be happy to
> "fix" that stuff for some reasonable definition of "fix". :-)
>
if there is a cleanup, awesome.. that would be really be good.
Regards,
NM
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-12-04 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 16:13 Robert P. J. Day
2012-12-04 19:08 ` menon.nishanth [this message]
2012-12-04 19:30 ` Robert P. J. Day
2012-12-04 19:36 ` menon.nishanth
2012-12-04 19:49 ` Robert P. J. Day
2012-12-04 20:53 ` Robert P. J. Day
2012-12-04 20:59 ` menon.nishanth
2012-12-04 21:03 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGo_u6q97PTW+FAUnTOw1h-Jx=ZbO_hqqfAyP-d8_7DkVZEnkQ@mail.gmail.com' \
--to=menon.nishanth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox