From: Paul Mundt <lethal@linux-sh.org>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: Chris Ball <cjb@laptop.org>, Magnus Damm <magnus.damm@gmail.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mmc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ian Molton <ian@mnementh.co.uk>, Magnus Damm <damm@opensource.se>,
linux-sh@vger.kernel.org
Subject: Re: outstanding TMIO MMC patches
Date: Wed, 05 Jan 2011 23:08:57 +0000 [thread overview]
Message-ID: <20110105230857.GH23889@linux-sh.org> (raw)
In-Reply-To: <4D24DFA8.3030201@arndnet.de>
On Wed, Jan 05, 2011 at 10:16:24PM +0100, Arnd Hannemann wrote:
> Am 05.01.2011 19:57, schrieb Chris Ball:
> > Arnd, can I take just patches 1/2 from your six-part series, and have
> > you send the rest through the arch/ maintainers later?
>
> Sure, should be no problem.
> Ah, just saw that you already pushed those two, thanks.
>
> @Paul:
> Maybe it would be best that you ACK those arch patches (if you think
> they are ok) and that they also go in via the mmc-next tree?
> Otherwise we would need to wait until mmc-next for .38 is merged in your trees,
> right?
>
If Chris prefers they go through the architecture side then that's not a
problem either. I'll be doing at least 2 merges during the merge window,
and this stuff is just adding in platform data, so it doesn't really
matter when it gets rolled in. Optionally if the MMC tree doesn't rebase
I can just set up a topic branch that branches off of that, roll these
patches on top of that, and you can just test that directly.
next prev parent reply other threads:[~2011-01-05 23:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 23:32 outstanding TMIO MMC patches Guennadi Liakhovetski
2010-12-29 13:35 ` Arnd Hannemann
2011-01-05 22:24 ` Chris Ball
2011-01-05 22:49 ` Chris Ball
2011-01-05 2:10 ` Magnus Damm
2011-01-05 4:53 ` Paul Mundt
2011-01-05 16:57 ` Chris Ball
2011-01-05 17:30 ` Paul Mundt
2011-01-05 18:57 ` Chris Ball
2011-01-05 21:16 ` Arnd Hannemann
2011-01-05 23:08 ` Paul Mundt [this message]
2011-01-05 23:31 ` Paul Mundt
2011-01-06 1:57 ` Magnus Damm
2011-01-05 22:57 ` Chris Ball
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=20110105230857.GH23889@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndnet.de \
--cc=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--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 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).