From: "J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: "J.E.J. Bottomley" <James.Bottomley@HansenPartnership.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 10:40:55 -0600 [thread overview]
Message-ID: <200211221640.gAMGetJ02979@localhost.localdomain> (raw)
In-Reply-To: Message from "Martin J. Bligh" <mbligh@aracnet.com> of "Fri, 22 Nov 2002 07:42:19 PST." <1047956111.1037950936@[10.10.2.3]>
mbligh@aracnet.com said:
> That's not true either. There are lots of header files under the
> include tree that aren't externally useful.
It may be honoured more in the breach than the observance, but it's a custom
nonetheless.
> 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.
> Que? How is include/asm-i386 any more "kernel core" than arch/i386?
Because the files are spreading. I think there's value to keeping something
tightly contained unless you're going to encourage others to use it.
Interfaces are dangerous things: If you release them into the wild
willy-nilly, they can come back and bite you (athough more often they just
bite other people).
James
next prev parent reply other threads:[~2002-11-22 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 0:00 [RFC] [PATCH] subarch cleanup 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 [this message]
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=200211221640.gAMGetJ02979@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.