From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Ian Molton <ian@mnementh.co.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 0/3] tmio: let platforms decide upon write-protection availability
Date: Sat, 22 May 2010 08:10:19 +0000 [thread overview]
Message-ID: <20100522081018.GD17814@linux-sh.org> (raw)
In-Reply-To: <20100522073332.GA17814@linux-sh.org>
On Sat, May 22, 2010 at 04:33:33PM +0900, Paul Mundt wrote:
> On Fri, May 21, 2010 at 12:38:27PM -0700, Andrew Morton wrote:
> > On Wed, 19 May 2010 20:35:57 +0200 (CEST)
> > Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> >
> > > No changes to patches themselves, just re-sending with an ack added.
> > >
> > > Applies on top of the
> > >
> > > "[PATCH 0/10] add DMA support to tmio_mmc, using dmaengine API, use it on SH"
> > >
> > > patch series.
> > >
> >
> > Paul, are you planning on merging the tem patches in the
> > above-mentioned series for 2.6.35-rc1?
> >
> Yes, they'll be in my next round of updates for -rc1. Since I don't have
> much else, I'll send those out today or tomorrow.
Since the 0/3 and 0/2 series also had all of the acked-bys and so on I
also took those. This at least lets us merge all of the sh platform
patches at the same time without any odd dependency ordering. The ARM
stuff I'll take care of separately after these have been merged.
next prev parent reply other threads:[~2010-05-22 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 9:52 [PATCH 0/3] tmio: let platforms decide upon write-protection Guennadi Liakhovetski
2010-05-11 9:52 ` [PATCH 1/3] tmio: add a platform flag to disable card write-protection Guennadi Liakhovetski
2010-05-11 12:04 ` [PATCH 1/3] tmio: add a platform flag to disable card Magnus Damm
2010-05-11 12:15 ` Guennadi Liakhovetski
2010-05-11 12:17 ` Magnus Damm
2010-05-11 9:52 ` [PATCH 2/3] mfd: pass platform flags down to the tmio_mmc driver Guennadi Liakhovetski
2010-05-13 16:08 ` [PATCH 2/3 v2] " Guennadi Liakhovetski
2010-05-11 9:52 ` [PATCH 3/3] sh: disable SD-card write-protection detection on kfr2r09 Guennadi Liakhovetski
2010-05-19 18:35 ` [PATCH 0/3] tmio: let platforms decide upon write-protection Guennadi Liakhovetski
2010-05-19 18:36 ` [PATCH 1/3] tmio: add a platform flag to disable card write-protection Guennadi Liakhovetski
2010-05-19 18:36 ` [PATCH 2/3 v2] mfd: pass platform flags down to the tmio_mmc driver Guennadi Liakhovetski
2010-05-19 18:36 ` [PATCH 3/3] sh: disable SD-card write-protection detection on kfr2r09 Guennadi Liakhovetski
2010-05-21 19:38 ` [PATCH 0/3] tmio: let platforms decide upon write-protection Andrew Morton
2010-05-22 7:33 ` [PATCH 0/3] tmio: let platforms decide upon write-protection availability Paul Mundt
2010-05-22 8:10 ` Paul Mundt [this message]
2010-05-25 19:09 ` [PATCH 0/3] tmio: let platforms decide upon write-protection Ian Molton
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=20100522081018.GD17814@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--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).