From: Bryan Wu <bryan.wu@analog.com>
To: Jesper Nilsson <Jesper.Nilsson@axis.com>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
Mikael Starvik <mikael.starvik@axis.com>
Subject: Re: [RFC] CRIS: Move header files from include to arch/cris
Date: Wed, 22 Oct 2008 10:38:50 +0800 [thread overview]
Message-ID: <48FE923A.70002@analog.com> (raw)
In-Reply-To: <20081021191736.GH24715@axis.com>
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@axis.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
next prev parent reply other threads:[~2008-10-22 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:42 [RFC] CRIS: Move header files from include to arch/cris Jesper Nilsson
2008-10-21 17:46 ` Mike Frysinger
2008-10-21 19:17 ` Jesper Nilsson
2008-10-21 19:23 ` Mike Frysinger
2008-10-22 2:38 ` Bryan Wu [this message]
2008-10-22 2:36 ` Bryan Wu
2008-10-22 3:11 ` Mike Frysinger
2008-10-29 17:34 ` [PATCH] [CRIS] Move header files from include to arch/cris/include Jesper Nilsson
2008-10-29 18:53 ` Sam Ravnborg
2008-10-30 12:12 ` Jesper Nilsson
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=48FE923A.70002@analog.com \
--to=bryan.wu@analog.com \
--cc=Jesper.Nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
--cc=sam@ravnborg.org \
--cc=vapier.adi@gmail.com \
/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