All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: linux-mmc@vger.kernel.org,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Simon Horman <horms@verge.net.au>,
	Arnd Hannemann <arnd@arndnet.de>,
	Magnus Damm <damm@opensource.se>,
	Paul Mundt <lethal@linux-sh.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 00/11] MMC DMA-API/dmaengine fixups
Date: Thu, 17 Feb 2011 02:54:54 +0000	[thread overview]
Message-ID: <20110217025454.GA22589@void.printf.net> (raw)
In-Reply-To: <AANLkTi=aU9B7Qo3RWifjJPLXR_E6hQm4A3iEdsLwhcgX@mail.gmail.com>

On Wed, Feb 16, 2011 at 10:04:20PM +0100, Linus Walleij wrote:
> Chris are you picking these up? Maybe the only way of getting
> some broad test of these cleanups is to push it into -next
> so it'll be noticed...

Hm, okay -- I've pushed the whole patchset to mmc-next.  (-next
is supposed to be a set of trees that each maintainer would be 
comfortable pushing to Linus immediately, though..)

I'd still like to see some ACKs for tmio/sh_mmc before pushing
these to mainline.  I'm CCing some folks who should be able to
help out with testing; if you can, would be much appreciated!

Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2011-02-17  2:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 15:06 [PATCH 00/11] MMC DMA-API/dmaengine fixups Linus Walleij
2011-02-16 21:04 ` Linus Walleij
2011-02-17  2:54   ` Chris Ball [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=20110217025454.GA22589@void.printf.net \
    --to=cjb@laptop.org \
    --cc=arnd@arndnet.de \
    --cc=damm@opensource.se \
    --cc=dan.j.williams@intel.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=horms@verge.net.au \
    --cc=lethal@linux-sh.org \
    --cc=linus.ml.walleij@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mmc@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.