public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Chris Ball <cjb@laptop.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
	Ian Molton <ian@mnementh.co.uk>,
	Magnus Damm <magnus.damm@gmail.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: outstanding tmio patches
Date: Sun, 27 Mar 2011 09:20:11 +0900	[thread overview]
Message-ID: <20110327002011.GC31554@verge.net.au> (raw)
In-Reply-To: <m3ipv7l07b.fsf@pullcord.laptop.org>

On Fri, Mar 25, 2011 at 10:54:48AM -0400, Chris Ball wrote:
> Hi,
> 
> On Fri, Mar 25 2011, Guennadi Liakhovetski wrote:
> > Hm, strange, now all patches should be correct - if the correct versions 
> > are taken. Let's do it easier: I've uploaded all 15 patches (14 mine and 1 
> > from Simon) as a quilt series to
> >
> > http://download.open-technology.de/tmio-for-2.6.39/
> 
> Thanks, I just needed to pull changes from Linus into mmc-next.
> 
> I've pushed everything out to mmc-next now.  If anyone else is able to
> grab mmc-next and supply a Tested-by: for their hardware, that'd be
> appreciated.

Hi,

I have done some tests on a Renesas Mackerel board (Guennadi likely has
one too) both with and without my "mmc, ARM: Add zboot from eSD support for
SuperH Mobile ARM" change - which needs to go through RMK's tree
and is the motivation for the " mmc: tmio_mmc: Move some defines into a
shared header" patch.

I didn't notice any problems.

FWIW

Tested-by: Simon Horman <horms@verge.net.au>

> Also, if anyone thinks that some of this should wait until .40, now's a
> good time to speak up.  :)

I have no particular objections though I do agree that it
is a lot of churn at this stage of the release cycle.

  reply	other threads:[~2011-03-27  0:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 14:15 outstanding tmio patches Guennadi Liakhovetski
2011-03-24  7:38 ` Guennadi Liakhovetski
2011-03-25  2:05 ` Chris Ball
2011-03-25  8:04   ` Guennadi Liakhovetski
2011-03-25 13:09     ` Chris Ball
2011-03-25 13:35       ` Guennadi Liakhovetski
2011-03-25 14:01   ` Chris Ball
2011-03-25 14:19     ` Guennadi Liakhovetski
2011-03-25 14:54       ` Chris Ball
2011-03-27  0:20         ` Simon Horman [this message]
2011-03-29 22:18       ` Chris Ball
2011-03-29 22:33         ` 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=20110327002011.GC31554@verge.net.au \
    --to=horms@verge.net.au \
    --cc=cjb@laptop.org \
    --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=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