[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0810211223j3b261e18m31127bdc8eb62cc5@mail.gmail.com>
Date: Tue, 21 Oct 2008 15:23:49 -0400
From: "Mike Frysinger" <vapier.adi@...il.com>
To: "Jesper Nilsson" <Jesper.Nilsson@...s.com>
Cc: "Sam Ravnborg" <sam@...nborg.org>,
LKML <linux-kernel@...r.kernel.org>,
"Mikael Starvik" <mikael.starvik@...s.com>,
"Bryan Wu" <Bryan.Wu@...log.com>
Subject: Re: [RFC] CRIS: Move header files from include to arch/cris
On Tue, Oct 21, 2008 at 15:17, 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 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.
when i grep for stuff, i often spend time doing both include/asm-$arch
and arch/$arch rather than looking only at headers or only at source
files ... so how things are organized below arch/$arch wouldnt affect
that aspect of how i work ...
-mike
--
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