From: Christoph Hellwig <hch@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Move scsi.h, hosts.h to include/linux/scsi ?
Date: Mon, 17 Feb 2003 12:18:40 +0000 [thread overview]
Message-ID: <20030217121840.A24543@infradead.org> (raw)
In-Reply-To: <20030216211422.GD8572@mars.ravnborg.org>; from sam@ravnborg.org on Sun, Feb 16, 2003 at 10:14:22PM +0100
On Sun, Feb 16, 2003 at 10:14:22PM +0100, Sam Ravnborg wrote:
> The usual rule within the kernel is that all header files useby more than
> one file, or at least by files spread all over the kernel,
> should be located in include/linux.
>
> Has this been considered for scsi.h, and if not so - why not?
> The same for hosts.h.
>
> Background for my question is that I'm doing some kbuild changes,
> and it is rather annoying to support include of scsi.h from all over.
> See the following snippet from: arch/i386/kernel/edd.c
It's not that simple. First the current hosts.h/scsi.h split doesn't make
sense. Second include/linux/scsi/ is a bad idea, either add more headers to
include/scsi/ or include/linux/.
I'd prefer either
include/scsi/core.h
include/scsi/hba.h
include/scsi/upper.h
or
include/linux/scsi.h (for everything)
plus a drivers/scsi/scsiP.h for stuff private to the midlayer.
next prev parent reply other threads:[~2003-02-17 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 21:14 Move scsi.h, hosts.h to include/linux/scsi ? Sam Ravnborg
2003-02-17 12:18 ` Christoph Hellwig [this message]
2003-02-17 12:53 ` Sam Ravnborg
2003-02-17 12:58 ` Christoph Hellwig
2003-02-17 13:07 ` Sam Ravnborg
2003-02-17 14:18 ` Christoph Hellwig
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=20030217121840.A24543@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@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