From: Christoph Hellwig <hch@infradead.org>
To: David Caldwell <david@porkrind.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Reimplement the SG_FLAG_LUN_INHIBIT flag in sg's SG_IOCTL.
Date: Mon, 19 Dec 2005 17:20:15 +0000 [thread overview]
Message-ID: <20051219172015.GA13438@infradead.org> (raw)
In-Reply-To: <1265DA04D7476A91BFE5A61E@bluey.local>
On Sun, Dec 18, 2005 at 06:44:16PM -0800, David Caldwell wrote:
> >scsi_request is hopefully not going to survive 2.6.16 so at this point
> >this patch is not interesting in this form.
>
> Have you started this work yet? I can re-implement the patch in the latest
> code base if you can point me to it.
In James' scsi-misc tree the work is almost done. All drivers but osst
and gdth are not using scsi_request anymore. Any implementation that
support the block/scsi_ioctl.c and drivers/scsi/sg.c SG_IO implementations
in that tree should be fine with when scsi_request is finally gone.
prev parent reply other threads:[~2005-12-19 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 21:54 [PATCH] Reimplement the SG_FLAG_LUN_INHIBIT flag in sg's SG_IOCTL David Caldwell
2005-12-17 12:28 ` Christoph Hellwig
2005-12-19 2:44 ` David Caldwell
2005-12-19 17:20 ` Christoph Hellwig [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=20051219172015.GA13438@infradead.org \
--to=hch@infradead.org \
--cc=david@porkrind.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