From: Chris Ball <cjb@laptop.org>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Thomas Abraham' <thomas.abraham@linaro.org>,
linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ben-linux@fluff.org
Subject: Re: [PATCH v2 1/2] mmc: sdhci-s3c: add default controller configuration
Date: Wed, 21 Sep 2011 08:18:34 -0400 [thread overview]
Message-ID: <m2boue6qcl.fsf@bob.laptop.org> (raw)
In-Reply-To: <002501cc784d$1618f110$424ad330$%kim@samsung.com> (Kukjin Kim's message of "Wed, 21 Sep 2011 19:56:16 +0900")
Hi,
On Wed, Sep 21 2011, Kukjin Kim wrote:
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
>
> Hi Chris,
>
> This is ok to me. Could you please pick this up in your tree so that I can
> pick 2nd patch up in my tree.
>
> As you know, this patch has no dependency with patch2/2 so that you can
> handle without any conflicts.
Thanks, pushed to mmc-next for 3.2.
I've been waiting for kernel.org to come back up, but I think later
today I'll just move mmc-next to git://dev.laptop.org/users/cjb/mmc,
so this will be available in linux-next soon.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] mmc: sdhci-s3c: add default controller configuration
Date: Wed, 21 Sep 2011 08:18:34 -0400 [thread overview]
Message-ID: <m2boue6qcl.fsf@bob.laptop.org> (raw)
In-Reply-To: <002501cc784d$1618f110$424ad330$%kim@samsung.com> (Kukjin Kim's message of "Wed, 21 Sep 2011 19:56:16 +0900")
Hi,
On Wed, Sep 21 2011, Kukjin Kim wrote:
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
>
> Hi Chris,
>
> This is ok to me. Could you please pick this up in your tree so that I can
> pick 2nd patch up in my tree.
>
> As you know, this patch has no dependency with patch2/2 so that you can
> handle without any conflicts.
Thanks, pushed to mmc-next for 3.2.
I've been waiting for kernel.org to come back up, but I think later
today I'll just move mmc-next to git://dev.laptop.org/users/cjb/mmc,
so this will be available in linux-next soon.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-09-21 12:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 7:09 [PATCH v2 0/2] Move sdhci-s3c platform helper into driver Thomas Abraham
2011-09-14 7:09 ` Thomas Abraham
2011-09-14 7:09 ` [PATCH v2 1/2] mmc: sdhci-s3c: add default controller configuration Thomas Abraham
2011-09-14 7:09 ` Thomas Abraham
2011-09-14 7:09 ` [PATCH v2 2/2] arm: samsung: remove sdhci default configuration setup platform helper Thomas Abraham
2011-09-14 7:09 ` Thomas Abraham
2011-09-21 10:56 ` [PATCH v2 1/2] mmc: sdhci-s3c: add default controller configuration Kukjin Kim
2011-09-21 10:56 ` Kukjin Kim
2011-09-21 12:18 ` Chris Ball [this message]
2011-09-21 12:18 ` Chris Ball
2011-09-21 12:27 ` Kukjin Kim
2011-09-21 12:27 ` Kukjin Kim
2011-09-21 10:51 ` [PATCH v2 0/2] Move sdhci-s3c platform helper into driver Kukjin Kim
2011-09-21 10:51 ` Kukjin Kim
2011-09-21 10:55 ` Thomas Abraham
2011-09-21 10:55 ` Thomas Abraham
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=m2boue6qcl.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=thomas.abraham@linaro.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 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.