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:40:58 -0400 [thread overview]
Message-ID: <3ED2FA6A.8040902@pobox.com> (raw)
In-Reply-To: <20030527063513.A2357@infradead.org>
Christoph Hellwig wrote:
> On Tue, May 27, 2003 at 01:19:36AM -0400, Jeff Garzik wrote:
>
>>This is too ambitious this close to 2.6-pre,
>
>
> No, it's not. Eihet we do it properly or not at all. Having to use
> different headers for 2.4,2.6and 2.7/2.8 is just extremly stupid.
I'm going to send my patch to Marcelo too, since it doesn't break
anything, and greatly reduces include annoyance for in-tree drivers
outside drivers/scsi.
> Also we have more intrusive stuff in scsi pending, 2.6.pre or not.
We'll see what akpm says...
Jeff
prev parent reply other threads:[~2003-05-27 5:27 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
2003-05-27 5:35 ` Christoph Hellwig
2003-05-27 5:40 ` 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=3ED2FA6A.8040902@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