From: Mike Christie <michaelc@cs.wisc.edu>
To: Kai.Makisara@kolumbus.fi, dougg@torque.net,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: [PATCH 0/5] convert st and sg to always use scatterlists take 2
Date: Thu, 15 Sep 2005 23:39:31 -0500 [thread overview]
Message-ID: <1126845571.9276.40.camel@max> (raw)
The following patches are a second (actually third if you count when I
tried to fixup all their duplicated code but broke a lot of features the
first time) try at converting sg and st to not use scsi_requests and
always use scatterlists.
It is not the grand cleanups I had hoped to do. It does allow us to
finish converting scsi-ml and LLDs without breaking anything though. It
is also a nice bit of cleanup for sg. I do hope to still move the the
ULDs to use the block layer blk_rq_map_user* functions for DIO and
copy_to/from_user cases so we can kill a lot of their code. And we
should be able to consolidate their buffer allocation code soon.
If these patches are ok, we just have to convert gdth, osst and cpqfc.
next reply other threads:[~2005-09-16 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 4:39 Mike Christie [this message]
2005-09-16 7:44 ` [PATCH 0/5] convert st and sg to always use scatterlists take 2 Mike Christie
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=1126845571.9276.40.camel@max \
--to=michaelc@cs.wisc.edu \
--cc=Kai.Makisara@kolumbus.fi \
--cc=dougg@torque.net \
--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.