From: Christoph Hellwig <hch@infradead.org>
To: "J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
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 16:57:56 +0000 [thread overview]
Message-ID: <20021122165756.A5626@infradead.org> (raw)
In-Reply-To: <200211221640.gAMGetJ02979@localhost.localdomain>; from James.Bottomley@HansenPartnership.com on Fri, Nov 22, 2002 at 10:40:55AM -0600
On Fri, Nov 22, 2002 at 10:40:55AM -0600, J.E.J. Bottomley wrote:
> > And every other header file is under the include path ... putting them
> > all mixed in with C files is just making a mess.
>
> No, look at e.g. SCSI. We have a scsi.h file in drivers/scsi which defines
> subsystem specific things that we only use within SCSI. We have
> include/scsi/scsi.h which defines things other subsystems can use.
Which is pretty stupid, btw. There are more than enough scsi HBA drivers
or emulation drivers outside drivers/scsi. I have a longstanding plan
to rationalize the scsi headers (the current state is really really messy),
and that includes moving everything but the truly midlayer-specific parts
like non-exported function to headers in include/scsi/.
next prev parent reply other threads:[~2002-11-22 16:51 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
2002-11-22 16:40 ` J.E.J. Bottomley
2002-11-22 16:57 ` Christoph Hellwig [this message]
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=20021122165756.A5626@infradead.org \
--to=hch@infradead.org \
--cc=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®