From: Chris Ball <cjb@laptop.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Simon Horman <horms@verge.net.au>,
linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH 5/5] ARM: mach-shmobile: ag5evm: SDHI requires waiting for idle
Date: Tue, 21 Jun 2011 12:37:56 -0400 [thread overview]
Message-ID: <m2tybjrvh7.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110621162735.GL7920@linux-sh.org> (Paul Mundt's message of "Wed, 22 Jun 2011 01:27:36 +0900")
Hi,
On Tue, Jun 21 2011, Paul Mundt wrote:
> On Tue, Jun 21, 2011 at 12:10:22PM -0400, Chris Ball wrote:
>> On Mon, Jun 20 2011, Simon Horman wrote:
>> > Dependencies:
>> > "mmc: sdhi: Add write16_hook"
>> > "ARM: mach-shmobile: ag5evm: consistently name sdhi info structures"
>>
>> Could I get your ACK for this one, so that I can merge patches 1/2/3/5
>> together via the MMC tree?
>>
> Well, this has a dependency on 4/5 which I've already applied. I was
> simply going to wait for 1-3 to be merged via your tree and then roll in
> this last one on top of that. If you want to take them all that's ok too,
> git should be able to deal with any merge conflicts fine.
Ah, okay -- I've pushed 1-3 now to mmc-next for 3.1, you can take 4-5.
(I was thinking I should try to avoid requiring you to wait for Linus
to pull MMC before you can send sh to him.)
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-06-21 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 23:00 [PATCH 0/5 v2] mmc: sdhi: Allow waiting for idle Simon Horman
2011-06-20 23:00 ` [PATCH 1/5] mmc: tmio: name 0xd8 as CTL_DMA_ENABLE Simon Horman
2011-06-20 23:00 ` [PATCH 2/5] mmc: tmio: Share register access functions Simon Horman
2011-06-20 23:00 ` [PATCH 3/5] mmc: sdhi: Add write16_hook Simon Horman
2011-06-21 0:36 ` Magnus Damm
2011-06-21 0:50 ` Simon Horman
2011-06-21 0:59 ` Magnus Damm
2011-06-21 1:13 ` Simon Horman
2011-06-21 1:36 ` Magnus Damm
2011-06-21 2:09 ` Simon Horman
2011-06-21 2:34 ` Magnus Damm
2011-06-20 23:00 ` [PATCH 4/5] ARM: mach-shmobile: ag5evm: consistently name sdhi info structures Simon Horman
2011-06-21 8:50 ` Paul Mundt
2011-06-20 23:00 ` [PATCH 5/5] ARM: mach-shmobile: ag5evm: SDHI requires waiting for idle Simon Horman
2011-06-21 16:10 ` Chris Ball
2011-06-21 16:27 ` Paul Mundt
2011-06-21 16:37 ` Chris Ball [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 6:06 [PATCH 0/5] mmc: sdhi: Allow " Simon Horman
2011-06-20 6:06 ` [PATCH 5/5] ARM: mach-shmobile: ag5evm: SDHI requires " 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=m2tybjrvh7.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--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