From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH 00/11 v2] mmc: tmio/sdhi: hotplug & PM
Date: Sat, 04 Feb 2012 20:06:20 -0500 [thread overview]
Message-ID: <m2ehua84xf.fsf@bob.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1202050147520.3770@axis700.grange> (Guennadi Liakhovetski's message of "Sun, 5 Feb 2012 01:56:25 +0100 (CET)")
Hi,
On Sat, Feb 04 2012, Guennadi Liakhovetski wrote:
> Thanks. Actually, it recently occurred to me, that patches 3 and 10 should
> actually be merged into one. So, if you like, I can produce a v3 with that
> taken into account. The result would be exactly the same, I literally
> would just apply #10 on top of #3 and commit the result with the same
> commit description as the v2 of #3.
Sure.
> Shall I also rebase v3 on top of mmx-next and fix the failing patch? The
> two ARM patches can be applied separately, but they have to go in after
> this series then. Either way is ok with me, pulling all via mmc has the
> advantage of not having to synchronise the pulls, but then the conflict
> probability rises of course.
I'm happy to take the ARM patches, but I'll need ACKs from the relevant
arch maintainers to do that.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-02-05 1:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 12:01 [PATCH 00/11 v2] mmc: tmio/sdhi: hotplug & PM Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 01/11] mmc: simplify mmc_cd_gpio_request() by removing two parameters Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 02/11] mmc: tmio: calculate the native hotplug condition only once Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 03/11] mmc: tmio_mmc: support the generic MMC GPIO card hotplug helper Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 04/11] mmc: sh_mobile_sdhi: pass card hotplug GPIO number to TMIO MMC Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 05/11] ARM: mach-shmobile: convert mackerel to use the generic MMC GPIO hotplug helper Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 06/11] ARM: mach-shmobile: convert ag5evm " Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 07/11] mmc: tmio_mmc: power status flag doesn't have to be exposed in platform data Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 08/11] mmc: tmio_mmc: remove unused sdio_irq_enabled flag Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 09/11] mmc: sh_mobile_sdhi: do not manage PM clocks manually Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 10/11] mmc: tmio: reconfigure the controller on runtime resume Guennadi Liakhovetski
2012-01-24 12:01 ` [PATCH 11/11] mmc: tmio: cosmetic: prettify the tmio_mmc_set_ios() function Guennadi Liakhovetski
2012-02-04 23:56 ` [PATCH 00/11 v2] mmc: tmio/sdhi: hotplug & PM Chris Ball
2012-02-05 0:56 ` Guennadi Liakhovetski
2012-02-05 1:06 ` Chris Ball [this message]
2012-02-05 1:36 ` 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=m2ehua84xf.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--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).