From: Chris Ball <cjb@laptop.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [GIT PULL] MMC fixes for 2.6.37
Date: Thu, 23 Dec 2010 19:13:11 +0000 [thread overview]
Message-ID: <20101223191311.GA9220@void.printf.net> (raw)
In-Reply-To: <AANLkTine-9YC7062cNaPG+iieBD2bcttx2b3sf3sveKP@mail.gmail.com>
Hi Kyungmin,
On Thu, Dec 23, 2010 at 06:17:50PM +0900, Kyungmin Park wrote:
> Can you include the s5pc210 external clock support?
As I said:
If Ben agrees, I'm happy to send it on.
If Ben stays silent, then I have to overrule him -- he's the maintainer
of this driver. I'm okay with doing that, but I'd like to do it by
shipping these patches in the next merge window and giving him (and
others who test the -rc series) time to disagree.
> without this, s5pc210 boards doesn't use the SDHCI.
But that's not a regression from earlier kernels (correct me if I'm
wrong). Adding support for a new board is a merge window task, not
a final-fixes-before-release task.
I'm sorry these patches have been waiting so long. I didn't realize
Ben would stay silent on them -- in future, I'll shorten my timeout
for an ACK from Ben.
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-12-23 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 8:56 [GIT PULL] MMC fixes for 2.6.37 Chris Ball
2010-12-23 9:17 ` Kyungmin Park
2010-12-23 19:13 ` Chris Ball [this message]
2010-12-28 2:37 ` 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=20101223191311.GA9220@void.printf.net \
--to=cjb@laptop.org \
--cc=ben-linux@fluff.org \
--cc=kmpark@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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