From: "J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
john stultz <johnstul@us.ibm.com>,
"J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] subarch cleanup
Date: Fri, 22 Nov 2002 09:00:47 -0600 [thread overview]
Message-ID: <200211221500.gAMF0lh02117@localhost.localdomain> (raw)
In-Reply-To: Message from "Martin J. Bligh" <mbligh@aracnet.com> of "Thu, 21 Nov 2002 10:35:43 PST." <228760000.1037903743@flay>
mbligh@aracnet.com said:
> > Why do you need to move the .h files?
> Because they're in a silly place now. They should be whereever all the
> other include files are.
> > CFLAGS += -Iarch/i386/$(MACHINE_H) -Iarch/i386/mach-generic
> > That should achieve the same effect?
> Header files go under include ....
That's not necessarily true. Externally useful header files go in include.
Header files only used internally to the subsystem go in local directories.
The reason I put them under arch/i386 is because I didn't want the guts of the
subarch splitup spilling into the kernel core.
While the subarch is local to i386, I think the headers should stay there. If
you want to make the subarch a global framework (and thus get agreement with
Russel and ARM to use it) then putting them under the global include
directories would probably make sense.
James
next prev parent reply other threads:[~2002-11-22 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 0:00 john stultz
2002-11-21 18:33 ` Sam Ravnborg
2002-11-21 18:35 ` Martin J. Bligh
2002-11-21 19:34 ` Russell King
2002-11-21 21:47 ` Martin J. Bligh
2002-11-22 15:00 ` J.E.J. Bottomley [this message]
2002-11-22 15:42 ` Martin J. Bligh
2002-11-22 16:40 ` J.E.J. Bottomley
2002-11-22 16:57 ` Christoph Hellwig
2002-11-22 17:20 ` Martin J. Bligh
2002-11-22 17:55 ` J.E.J. Bottomley
2002-11-21 18:55 ` john stultz
2002-11-21 19:15 ` Sam Ravnborg
2002-11-21 20:27 ` Alan Cox
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=200211221500.gAMF0lh02117@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=sam@ravnborg.org \
/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
all inboxes | Powered by JetHome®