From: Simon Horman <horms@verge.net.au>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Ian Molton <ian@mnementh.co.uk>,
linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
Chris Ball <cjb@laptop.org>, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH 0/6] mmc: split the tmio driver into several modules
Date: Tue, 22 Mar 2011 22:06:24 +0000 [thread overview]
Message-ID: <20110322220623.GJ2423@verge.net.au> (raw)
In-Reply-To: <20110322122850.GA26099@linux-sh.org>
On Tue, Mar 22, 2011 at 09:28:50PM +0900, Paul Mundt wrote:
> On Tue, Mar 22, 2011 at 02:31:31PM +0900, Simon Horman wrote:
> > On Mon, Mar 21, 2011 at 12:38:10PM +0100, Guennadi Liakhovetski wrote:
> > > Hi Chris, Ian
> > >
> > > AFAICS there are currently still a few tmio patch-series outstanding:
> > >
> > > From: Guennadi Liakhovetski <g.liakhovetski <at> gmx.de>
> > > Subject: [PATCH 0/2] tmio_mmc: improve DMA reliability
> > > http://thread.gmane.org/gmane.linux.kernel.mmc/6485
> > >
> > > From: Simon Horman <horms <at> verge.net.au>
> > > Subject: [PATCH 0/4] [rfc v3] mmc, ARM: Add zboot from eSD support for SuperH Mobile ARM
> > > http://thread.gmane.org/gmane.linux.kernel.mmc/6664
> >
> > IMHO, Patch 1-3 are ready and can either be merged through the MMC
> > or one of Paul's trees. Although I should note that patches
> > 2 and 3 include changes to arch/arm/boot/compressed/mmcif-sh7372.c and
> > arch/sh/boot/romimage/mmcif-sh7724.c.
> >
> I'm having a hard time working out what these arbitrary 1-3 numbers map
> to in terms of actual series and patch numbers. As far as things with an
> sh or rmobile impact I see:
>
> sh: ecovec: use the CONFIG_MMC_TMIO symbols instead of MFD
>
> and
>
> [rfc v3] mmc, ARM: Add zboot from eSD support for SuperH Mobile ARM
>
> although it's not obvious how the latter is tied to a TMIO dependency
> (some SDHI header thing?).
>
> I'm happy to take the ecovec patch whenever, since it doesn't really hurt
> anything. Anything touching drivers/mmc I obviously prefer to go via Chris.
>
> I got buried in the fbdev patch queue today, so I'll be catching up on sh and
> rmobile stuff tomorrow. You're free to work out amongst yourselves what gets
> applied where in which order, or I'll simply guess.
Hi Paul,
By 1-3 I was referring to the first three patches of
[PATCH 0/4] [rfc v3] mmc, ARM: Add zboot from eSD support for SuperH Mobile ARM
That is:
[PATCH 1/4] mmc: tmio_mmc: Move some defines into a shared header
[PATCH 2/4] mmc, ARM: Rename SuperH Mobile ARM zboot helpers
[PATCH 3/4] mmc: Add MMC_PROGRESS_*
And by patch 4 I was referring to
[PATCH 4/4 v5] mmc, ARM: Add zboot from eSD support for SuperH Mobile
I apologise for that being as clear as mud.
Magnus raised a build issue with the series since my previous email.
I will investigate that and reply to him ASAP. Its probably best
to hold all the patches until then.
With regards to
[PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead of MFD
it looks like Magnus raised a few issues and Guennadi is going to repost
the patch. But I could be wrong.
next prev parent reply other threads:[~2011-03-22 22:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 7:51 [PATCH 0/6] mmc: split the tmio driver into several modules Guennadi Liakhovetski
2011-03-11 7:51 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Guennadi Liakhovetski
2011-03-12 16:05 ` Magnus Damm
2011-03-12 22:48 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD Guennadi Liakhovetski
2011-03-13 3:57 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Magnus Damm
2011-03-13 22:51 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD Guennadi Liakhovetski
2011-03-15 9:01 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Magnus Damm
2011-03-16 11:09 ` Ian Molton
2011-03-16 12:37 ` Magnus Damm
2011-03-21 11:19 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead of Guennadi Liakhovetski
2011-03-12 16:18 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead Magnus Damm
2011-03-12 23:00 ` Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a Guennadi Liakhovetski
2011-03-13 4:14 ` Magnus Damm
2011-03-14 8:01 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to Guennadi Liakhovetski
2011-03-15 9:09 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a Magnus Damm
2011-03-11 7:52 ` [PATCH 4/6] ARM: mach-shmobile: convert boards to use Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 5/6] sh: convert boards to use linux/mmc/sh_mobile_sdhi.h Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 6/6] mfd: remove now redundant sh_mobile_sdhi.h header Guennadi Liakhovetski
2011-03-15 21:25 ` [PATCH 0/6] mmc: split the tmio driver into several modules Ian Molton
2011-03-21 11:38 ` Guennadi Liakhovetski
2011-03-22 5:31 ` Simon Horman
2011-03-22 12:28 ` Paul Mundt
2011-03-22 22:06 ` Simon Horman [this message]
2011-03-23 14:54 ` Paul Mundt
2011-03-23 22:42 ` Simon Horman
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=20110322220623.GJ2423@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 \
/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).