From: Paul Mundt <lethal@linux-sh.org>
To: Simon Horman <horms@verge.net.au>
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: Wed, 23 Mar 2011 23:54:53 +0900 [thread overview]
Message-ID: <20110323145453.GA12106@linux-sh.org> (raw)
In-Reply-To: <20110322220623.GJ2423@verge.net.au>
On Wed, Mar 23, 2011 at 07:06:24AM +0900, Simon Horman wrote:
> 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.
>
Ok, that makes a bit more sense, thanks for clearing it up.
> 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.
>
It looks like 1/4 is going to have to go through the MMC tree, and will
have to layer on top of Guennadi's current patch stack. He's done a good
job of summarizing the outstanding bits, so it should be trivial to build
on top of that.
Once 1/4 is merged I can easily merge 2 and 3/4 at pretty much any time
during the -rc window, although I'd prefer to have it sorted out by -rc2
or -rc3 at the latest. This will just leave 4/4 for rmk's patch tracker
and its respective scheduling.
For now I'll punt the series from patchwork and await a resend with 1/4
rebased in such a way that it can trivially be picked up by the MMC tree.
> 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.
>
Yes, already dealt with separately.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Simon Horman <horms@verge.net.au>
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: Wed, 23 Mar 2011 14:54:53 +0000 [thread overview]
Message-ID: <20110323145453.GA12106@linux-sh.org> (raw)
In-Reply-To: <20110322220623.GJ2423@verge.net.au>
On Wed, Mar 23, 2011 at 07:06:24AM +0900, Simon Horman wrote:
> 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.
>
Ok, that makes a bit more sense, thanks for clearing it up.
> 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.
>
It looks like 1/4 is going to have to go through the MMC tree, and will
have to layer on top of Guennadi's current patch stack. He's done a good
job of summarizing the outstanding bits, so it should be trivial to build
on top of that.
Once 1/4 is merged I can easily merge 2 and 3/4 at pretty much any time
during the -rc window, although I'd prefer to have it sorted out by -rc2
or -rc3 at the latest. This will just leave 4/4 for rmk's patch tracker
and its respective scheduling.
For now I'll punt the series from patchwork and await a resend with 1/4
rebased in such a way that it can trivially be picked up by the MMC tree.
> 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.
>
Yes, already dealt with separately.
next prev parent reply other threads:[~2011-03-23 14:55 UTC|newest]
Thread overview: 52+ 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 ` Guennadi Liakhovetski
2011-03-11 7:51 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Guennadi Liakhovetski
2011-03-11 7:51 ` Guennadi Liakhovetski
2011-03-12 16:05 ` Magnus Damm
2011-03-12 16:05 ` Magnus Damm
2011-03-12 22:48 ` Guennadi Liakhovetski
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 3:57 ` Magnus Damm
2011-03-13 22:51 ` Guennadi Liakhovetski
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-15 9:01 ` Magnus Damm
2011-03-16 11:09 ` Ian Molton
2011-03-16 12:37 ` Magnus Damm
2011-03-16 12:37 ` Magnus Damm
2011-03-21 11:19 ` Guennadi Liakhovetski
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 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 of MFD Magnus Damm
2011-03-12 16:18 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead Magnus Damm
2011-03-12 23:00 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead of MFD Guennadi Liakhovetski
2011-03-12 23:00 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a standard platform driver 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 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a standard platform driver Magnus Damm
2011-03-13 4:14 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a Magnus Damm
2011-03-14 8:01 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a standard platform driver Guennadi Liakhovetski
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 standard platform driver Magnus Damm
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 linux/mmc/sh_mobile_sdhi.h Guennadi Liakhovetski
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 ` Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 6/6] mfd: remove now redundant sh_mobile_sdhi.h header Guennadi Liakhovetski
2011-03-11 7:52 ` 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-21 11:38 ` Guennadi Liakhovetski
2011-03-22 5:31 ` Simon Horman
2011-03-22 5:31 ` Simon Horman
2011-03-22 12:28 ` Paul Mundt
2011-03-22 12:28 ` Paul Mundt
2011-03-22 22:06 ` Simon Horman
2011-03-22 22:06 ` Simon Horman
2011-03-23 14:54 ` Paul Mundt [this message]
2011-03-23 14:54 ` Paul Mundt
2011-03-23 22:42 ` Simon Horman
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=20110323145453.GA12106@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=ian@mnementh.co.uk \
--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 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.