From: Jeff Garzik <jgarzik@pobox.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: RFC: move hosts.h, scsi.h
Date: Thu, 22 May 2003 21:54:52 -0400 [thread overview]
Message-ID: <3ECD7F6C.8010702@pobox.com> (raw)
In-Reply-To: <20030522230414.A1916@pclin040.win.tue.nl>
Andries Brouwer wrote:
> On Thu, May 22, 2003 at 04:34:53PM -0400, Jeff Garzik wrote:
>
>
>>I request permission to do the following:
>>
>>1) bk mv drivers/scsi/scsi.h include/linux
>>2) bk mv drivers/scsi/hosts.h include/linux/scsi_hosts.h
>>3) bk mv drivers/scsi/scsi_obsolete.h include/linux
>>4) create shell drivers/scsi/{...}.h that includes just-moved files, so
>>to preserve full driver source compatibility.
>>5) edit include/linux/scsi.h to include <linux/scsi_obsolete.h> not
>>"scsi_obsolete.h"
>>
>>Objections/comments?
>
>
> No doubt with the goal of removing all those ugly
> #include "../../scsi/hosts.h"
Yes, and nasty -I hacks in Makefiles.
> A good plan.
>
> I think point 5) is superfluous.
> (That is, I think by default "foo.h" is found in the directory
> of the including file.)
I thought so too, but gcc disagreed :)
I think '#include <linux/...>' is more clean, too.
> Probably this would mean that usb/storage/Makefile no longer
> needs -Idrivers/scsi, provided the "scsi.h" there is replaced
> by <linux/scsi.h>.
Yep
> Remains the vague objection: it is a bit confusing to have
> several files of the same name. And in case some compilation
> has both include/linux and include/scsi on the include path
> there are ordering restraints. Maybe life will be easier
> if you invent some other name like scsidefs.h.
Easily done and a good objection/suggestion. I'm using
scsi_{defs,hosts,obsolete}.h in my local tree right now.
Jeff
prev parent reply other threads:[~2003-05-23 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 20:34 RFC: move hosts.h, scsi.h Jeff Garzik
2003-05-22 20:45 ` Christoph Hellwig
2003-05-22 21:59 ` Andries Brouwer
2003-05-23 1:52 ` Jeff Garzik
2003-05-22 21:04 ` Andries Brouwer
2003-05-23 1:54 ` Jeff Garzik [this message]
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=3ECD7F6C.8010702@pobox.com \
--to=jgarzik@pobox.com \
--cc=aebr@win.tue.nl \
--cc=linux-scsi@vger.kernel.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.