From: Stephen Warren <swarren@wwwdotorg.org>
To: Chris Ball <cjb@laptop.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Colin Cross <ccross@android.com>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH REPOST 1/2] mmc: tegra: use bus-width property instead of support-8bit
Date: Wed, 06 Jun 2012 11:34:48 -0600 [thread overview]
Message-ID: <4FCF94B8.6000400@wwwdotorg.org> (raw)
In-Reply-To: <20120606135647.GA3423@void.printf.net>
On 06/06/2012 07:56 AM, Chris Ball wrote:
> On Mon, Jun 04, 2012 at 12:32:34PM -0600, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Update the driver to parse the new unified bus-width property introduced
>> in commit 7f21779 "mmc: dt: Consolidate DT bindings", instead of the legacy
>> support-8bit property.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> Chris, It's probably easiest conflict-wise if I take this through the Tegra
>> tree. (Note: When I posted this series before, I said there shouldn't be any
>> conflicts if you take them through the MMC tree. That's probably still true,
>> but unforseen future conflicts seem more likely in the .dts files in the
>> second patch than sdhci-tegra.c in this patch, so the Tegra tree may make
>> more sense). Since the second patch depends on the first, it's easiest if
>> these go in through the same tree. Does this sound OK?
>
> Yes, makes sense -- taking this via the Tegra tree is fine:
>
> Acked-by: Chris Ball <cjb@laptop.org>
Thanks. I have applied the series.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH REPOST 1/2] mmc: tegra: use bus-width property instead of support-8bit
Date: Wed, 06 Jun 2012 11:34:48 -0600 [thread overview]
Message-ID: <4FCF94B8.6000400@wwwdotorg.org> (raw)
In-Reply-To: <20120606135647.GA3423@void.printf.net>
On 06/06/2012 07:56 AM, Chris Ball wrote:
> On Mon, Jun 04, 2012 at 12:32:34PM -0600, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Update the driver to parse the new unified bus-width property introduced
>> in commit 7f21779 "mmc: dt: Consolidate DT bindings", instead of the legacy
>> support-8bit property.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> Chris, It's probably easiest conflict-wise if I take this through the Tegra
>> tree. (Note: When I posted this series before, I said there shouldn't be any
>> conflicts if you take them through the MMC tree. That's probably still true,
>> but unforseen future conflicts seem more likely in the .dts files in the
>> second patch than sdhci-tegra.c in this patch, so the Tegra tree may make
>> more sense). Since the second patch depends on the first, it's easiest if
>> these go in through the same tree. Does this sound OK?
>
> Yes, makes sense -- taking this via the Tegra tree is fine:
>
> Acked-by: Chris Ball <cjb@laptop.org>
Thanks. I have applied the series.
next prev parent reply other threads:[~2012-06-06 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 18:32 [PATCH REPOST 1/2] mmc: tegra: use bus-width property instead of support-8bit Stephen Warren
2012-06-04 18:32 ` Stephen Warren
[not found] ` <1338834755-6900-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-04 18:32 ` [PATCH REPOST 2/2] ARM: dt: tegra: remove legacy support-8bit property Stephen Warren
2012-06-04 18:32 ` Stephen Warren
2012-06-06 13:56 ` [PATCH REPOST 1/2] mmc: tegra: use bus-width property instead of support-8bit Chris Ball
2012-06-06 13:56 ` Chris Ball
2012-06-06 17:34 ` Stephen Warren [this message]
2012-06-06 17:34 ` Stephen Warren
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=4FCF94B8.6000400@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=swarren@nvidia.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.