[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48FE923A.70002@analog.com>
Date: Wed, 22 Oct 2008 10:38:50 +0800
From: Bryan Wu <bryan.wu@...log.com>
To: Jesper Nilsson <Jesper.Nilsson@...s.com>
CC: Mike Frysinger <vapier.adi@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
LKML <linux-kernel@...r.kernel.org>,
Mikael Starvik <mikael.starvik@...s.com>
Subject: Re: [RFC] CRIS: Move header files from include to arch/cris
Jesper Nilsson wrote:
> On Tue, Oct 21, 2008 at 07:46:18PM +0200, Mike Frysinger wrote:
>
>> On Tue, Oct 21, 2008 at 12:42, Jesper Nilsson <jesper.nilsson@...s.com> wrote:
>>
>>> That means that the machine dependent header files are moved to
>>> arch/cris/mach-{fs,a3}/include, while the common and architecture
>>> dependent files are moved to arch/cris/include.
>>>
>>> It is mainly this I'd like some input on, since most other ports
>>> that have moved their header files have put all headers in arch/*/include.
>>>
>> that seems like a fairly obvious good idea to me ... i'm thinking we
>> should do it for Blackfin as well ...
>>
>
> I'm still not decided, my main reason for following Blackfin and ARM
> was that it seemed good to collect all mach-specific files in one place
> in the tree.
>
> However, keeping them in the same place makes it easy to grep through,
> something I use quite frequently.
>
>
For grepping, just use "find arch/blackfin -name *.h | xargs grep ......."
I think is ok for you, though "grep -r xxxx arch/blackfin/include" is
more simple.
-Bryan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists