From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [bk patches] move scsi headers
Date: Tue, 27 May 2003 01:19:36 -0400 [thread overview]
Message-ID: <3ED2F568.7060501@pobox.com> (raw)
In-Reply-To: <20030527061444.A1905@infradead.org>
Christoph Hellwig wrote:
> On Mon, May 26, 2003 at 11:42:39PM -0400, Jeff Garzik wrote:
>
>>James, please do a
>>
>> bk pull bk://kernel.bkbits.net/jgarzik/scsi-misc-2.5
>
>
> Also I already told you that the header organisation is crap. include/scsi
> exists for a reason, the scsi.h/host.h split is broken and scsi_obsolete.h
> should go away not moved around.
>
> If you want to do something useful you could start removing scsi_obsolete.h,
> make the scsi core and scsi.h/hosts.h clean of the obsolete typedefs first.
This is too ambitious this close to 2.6-pre, and there is also
disagreement about use of include/scsi. I took the minimal patch.
As we are very close to 2.6-pre, your suggestions may even want waiting
until 2.7. I'll leave it up to James...
Consider this a first step. The world does not change in a day :)
Jeff
next prev parent reply other threads:[~2003-05-27 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 3:42 [bk patches] move scsi headers Jeff Garzik
2003-05-27 5:14 ` Christoph Hellwig
2003-05-27 5:19 ` Jeff Garzik [this message]
2003-05-27 5:35 ` Christoph Hellwig
2003-05-27 5:40 ` Jeff Garzik
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=3ED2F568.7060501@pobox.com \
--to=jgarzik@pobox.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox