mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	john stultz <johnstul@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] subarch cleanup
Date: Fri, 22 Nov 2002 07:42:19 -0800	[thread overview]
Message-ID: <1047956111.1037950936@[10.10.2.3]> (raw)
In-Reply-To: <200211221500.gAMF0lh02117@localhost.localdomain>

>> 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.

That's not true either. There are lots of header files under the
include tree that aren't externally useful. And every other header
file is under the include path ... putting them all mixed in with
C files is just making a mess.

> 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.

Que? How is include/asm-i386 any more "kernel core" than arch/i386?

M.


  reply	other threads:[~2002-11-22 15:38 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
2002-11-22 15:42       ` Martin J. Bligh [this message]
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='1047956111.1037950936@[10.10.2.3]' \
    --to=mbligh@aracnet.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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®