From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [bk patches] move scsi headers
Date: Tue, 27 May 2003 06:14:44 +0100 [thread overview]
Message-ID: <20030527061444.A1905@infradead.org> (raw)
In-Reply-To: <20030527034239.GA16376@gtf.org>; from jgarzik@pobox.com on Mon, May 26, 2003 at 11:42:39PM -0400
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.
next prev parent reply other threads:[~2003-05-27 5:01 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 [this message]
2003-05-27 5:19 ` Jeff Garzik
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=20030527061444.A1905@infradead.org \
--to=hch@infradead.org \
--cc=jgarzik@pobox.com \
--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