From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mmc@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Ian Molton <ian@mnementh.co.uk>,
Magnus Damm <magnus.damm@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Philipp Zabel <philipp.zabel@gmail.com>
Subject: Re: [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine
Date: Thu, 13 May 2010 04:06:44 +0000 [thread overview]
Message-ID: <20100513000644.92511b9b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100513064421.GA10731@linux-sh.org>
On Thu, 13 May 2010 15:44:21 +0900 Paul Mundt <lethal@linux-sh.org> wrote:
> On Thu, May 13, 2010 at 08:42:42AM +0200, Guennadi Liakhovetski wrote:
> > On Wed, 12 May 2010, Andrew Morton wrote:
> >
> > > On Tue, 11 May 2010 12:07:07 +0200 (CEST)
> > > Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> > >
> > > > 2.6.35 release is approaching and Ian hasn't found time yet to review this
> > > > series, so I was wondering, maybe you could take it into mm at least for
> > > > now?
> > >
> > > Well I did, but I don't know how useful that was.
> > >
> > > WHo is the most appropriate tree-maintainer to review and possibly
> > > merge these?
> >
> > Samuel has already acked the MFD patch:
> >
> > http://article.gmane.org/gmane.linux.ports.sh.devel/7985
> >
> > (please, add this his ack to the patch too). Most of the patches in the
> > series are SuperH- or SH-Mobile specific, which makes Paul (added to CC)
> > the perfect candidate to review them. There is only one tmio-specific
> > patch, and it is also the most complicated one. You or Paul can certainly
> > just follow it to verify, that it doesn't introduce any regressions. I can
> > also confirm it, because I also tested the patched driver without DMA
> > loaded, and it worked just like before in PIO mode. It would, however, be
> > great to test the patches on a non-sdhi hardware, of which none of us,
> > probably, has any. I added Philipp Zabel to CC, who has contributed a few
> > patches to tmio_mmc in the past, perhaps, he still has access to the
> > hardware and could test these patches.
> >
> I don't have any problems taking all of the SH and SDHI related bits, but
> since they all depend on the tmio_mmc change I haven't picked them up
> yet. They'll likely continue to sit in my patch queue until something
> happens with the tmio_mmc changes. Given the response times we've had
> with any tmio related changes in the past I'm not exactly betting on a
> speedy resolution..
argh. Patches have names, guys. What are "the tmio_mmc changes" and
where are they?
next prev parent reply other threads:[~2010-05-13 4:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 14:32 [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine API, Guennadi Liakhovetski
2010-05-07 14:32 ` [PATCH 4a/9 v3] sh: prepare the SDHI MFD driver to pass DMA Guennadi Liakhovetski
2010-05-10 23:04 ` Samuel Ortiz
2010-05-07 14:32 ` [PATCH 4b/9 v3] MMC: add DMA support to tmio_mmc driver, when used Guennadi Liakhovetski
2010-05-11 10:07 ` [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine API, Guennadi Liakhovetski
2010-05-11 12:38 ` [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine API, use it on SH Paul Mundt
2010-05-12 22:55 ` [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine Andrew Morton
2010-05-13 6:42 ` [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine API, Guennadi Liakhovetski
2010-05-13 6:44 ` [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine API, use it on SH Paul Mundt
2010-05-13 4:06 ` Andrew Morton [this message]
2010-05-13 7:18 ` [PATCH 0/9 v3] add DMA support to tmio_mmc, using dmaengine API, Guennadi Liakhovetski
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=20100513000644.92511b9b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=philipp.zabel@gmail.com \
--cc=sameo@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).