From: Christoph Hellwig <hch@infradead.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
hch@infradead.org, James.Bottomley@SteelEye.com,
linux-scsi@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: [PATCH 0/19] clean ups on the drivers
Date: Tue, 15 May 2007 10:01:16 +0100 [thread overview]
Message-ID: <20070515090116.GA9297@infradead.org> (raw)
In-Reply-To: <4648829A.10602@s5r6.in-berlin.de>
On Mon, May 14, 2007 at 05:39:06PM +0200, Stefan Richter wrote:
> FUJITA Tomonori wrote:
> >> > There are two patches for each driver, removing the non-use-sg code
> >> > and converting to use the accessors.
> ...
> > I merged the two. And I finished cleaning up 35 drivers in total.
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tomo/linux-2.6-bidi.git cleanups
>
> According to what I see via gitweb, at least usb-storage, ieee1394/sbp2,
> and firewire/fw-sbp2 weren't treated yet. If somebody does so for the
> latter two: The shost->shost_gendev.parent has to be changed for
> scsi_dma_{un}map. I don't know if this can be done without breaking
> anything.
That means they should not be converted to these helpers for now.
Personally I'd still love to have the dma mapping routines to work on
any given struct device but walking up the parent chain until an iommu
is found, but that was vetoed when first proposed.
next prev parent reply other threads:[~2007-05-15 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 10:05 [PATCH 0/19] clean ups on the drivers FUJITA Tomonori
2007-05-12 15:30 ` Christoph Hellwig
2007-05-13 3:30 ` FUJITA Tomonori
2007-05-14 14:40 ` FUJITA Tomonori
2007-05-14 15:39 ` Stefan Richter
2007-05-14 22:36 ` FUJITA Tomonori
2007-05-15 9:01 ` Christoph Hellwig [this message]
2007-05-15 11:54 ` James Bottomley
2007-05-15 11:57 ` Christoph Hellwig
2007-05-15 16:57 ` James Bottomley
2007-05-15 20:37 ` David Miller
2007-05-15 20:49 ` James Bottomley
2007-05-22 23:32 ` FUJITA Tomonori
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=20070515090116.GA9297@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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