From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Chris Ball <cjb@laptop.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>
Subject: Re: [PATCH] MMC: fix sdhci-dove removal
Date: Mon, 29 Oct 2012 23:16:07 +0100 [thread overview]
Message-ID: <508F0027.1010102@gmail.com> (raw)
In-Reply-To: <87vcdtosnx.fsf@octavius.laptop.org>
On 10/29/2012 10:49 PM, Chris Ball wrote:
> On Mon, Oct 29 2012, Russell King - ARM Linux wrote:
>> Anyway, here's a replacement patch, updated against my cubox tree but
>> lacking the cubox gpio changes for it. Un-tested through: (a) I can't
>> test this on its own on the cubox, (b) I don't have a separate dove
>> tree to test it against and my disk space is all but out at the moment
>> for yet another build tree...
>
> Compile-tested and pushed to mmc-next, and I'll submit it for 3.7 if
> I get a Tested-by from someone like Sebastian (CC'd), or for 3.8 if I
> don't. (I'll add sdhci-pltfm API rework to my TODO list, too.)
Chris, Russell,
obviously I am not the one to ask for a Tested-by because it was my
patch that originally caused all the trouble. My apologies for this!
Anyway, I did test the patch on 3.7-rc3 and except that you need a
3-way git am because of a one-line offset, sdhci-dove runs just fine.
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MMC: fix sdhci-dove removal
Date: Mon, 29 Oct 2012 23:16:07 +0100 [thread overview]
Message-ID: <508F0027.1010102@gmail.com> (raw)
In-Reply-To: <87vcdtosnx.fsf@octavius.laptop.org>
On 10/29/2012 10:49 PM, Chris Ball wrote:
> On Mon, Oct 29 2012, Russell King - ARM Linux wrote:
>> Anyway, here's a replacement patch, updated against my cubox tree but
>> lacking the cubox gpio changes for it. Un-tested through: (a) I can't
>> test this on its own on the cubox, (b) I don't have a separate dove
>> tree to test it against and my disk space is all but out at the moment
>> for yet another build tree...
>
> Compile-tested and pushed to mmc-next, and I'll submit it for 3.7 if
> I get a Tested-by from someone like Sebastian (CC'd), or for 3.8 if I
> don't. (I'll add sdhci-pltfm API rework to my TODO list, too.)
Chris, Russell,
obviously I am not the one to ask for a Tested-by because it was my
patch that originally caused all the trouble. My apologies for this!
Anyway, I did test the patch on 3.7-rc3 and except that you need a
3-way git am because of a one-line offset, sdhci-dove runs just fine.
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
next prev parent reply other threads:[~2012-10-29 22:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 9:43 [PATCH] MMC: fix sdhci-dove removal Russell King - ARM Linux
2012-10-15 9:43 ` Russell King - ARM Linux
2012-10-15 10:37 ` Russell King - ARM Linux
2012-10-15 10:37 ` Russell King - ARM Linux
2012-10-15 10:44 ` Russell King - ARM Linux
2012-10-15 10:44 ` Russell King - ARM Linux
2012-10-15 14:58 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-15 14:58 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-15 15:07 ` Russell King - ARM Linux
2012-10-15 15:07 ` Russell King - ARM Linux
2012-10-29 21:10 ` Chris Ball
2012-10-29 21:10 ` Chris Ball
2012-10-29 21:43 ` Russell King - ARM Linux
2012-10-29 21:43 ` Russell King - ARM Linux
2012-10-29 21:49 ` Chris Ball
2012-10-29 21:49 ` Chris Ball
2012-10-29 22:16 ` Sebastian Hesselbarth [this message]
2012-10-29 22:16 ` Sebastian Hesselbarth
2012-10-29 22:20 ` Chris Ball
2012-10-29 22:20 ` 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=508F0027.1010102@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sebastian.hesselbarth@googlemail.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 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.