From: Stephen Warren <swarren@wwwdotorg.org>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Chris Ball <cjb@laptop.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Pritesh Raithatha <praithatha@nvidia.com>
Subject: Re: [PATCH 2/4] ARM: tegra: add SDHCI support for Dalmore
Date: Wed, 20 Feb 2013 12:16:19 -0700 [thread overview]
Message-ID: <51252103.70202@wwwdotorg.org> (raw)
In-Reply-To: <512520A2.5060005@nvidia.com>
On 02/20/2013 12:14 PM, Rhyland Klein wrote:
> On 2/20/2013 2:07 PM, Stephen Warren wrote:
>> On 02/20/2013 11:35 AM, Rhyland Klein wrote:
>>> Based on changes by: Pritesh Raithatha <praithatha@nvidia.com>
>>> Signed-off-by: Rhyland Klein <rklein@nvidia.com>
>> A patch description would be useful here. Something simple like:
>>
>> Dalmore has a built-in eMMC device and a user-accessible SD card slot.
>> Add device tree nodes to enable these.
>>
>> The same rebasing comment will apply here too.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Will update patch description for next series.
>
> I can rebase on the cpp usage, but for some stuff like the #define
> replacements, it sounded like things were still being hashed out (like
> .h location, include paths, etc) so I figured its safer not to base on
> those initially. If they are settled by the time i send this out again,
> i can use them as a base.
Yes, it's not all 100% settled yet; I pointed it out more as a heads-up
that I might ask you to rebase later. There's no need to actively rebase
just yet.
next prev parent reply other threads:[~2013-02-20 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 18:35 [PATCH 0/4] Tegra114 Add Minimal SDHCI support Rhyland Klein
2013-02-20 18:35 ` [PATCH 2/4] ARM: tegra: add SDHCI support for Dalmore Rhyland Klein
2013-02-20 19:07 ` Stephen Warren
2013-02-20 19:14 ` Rhyland Klein
2013-02-20 19:16 ` Stephen Warren [this message]
2013-03-06 21:19 ` Stephen Warren
[not found] ` <1361385317-6020-1-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-20 18:35 ` [PATCH 1/4] ARM tegra: add SDHCI nodes with common properties Rhyland Klein
2013-02-20 19:06 ` Stephen Warren
2013-02-20 18:35 ` [PATCH 3/4] mmc: host: sdhci-tegra: cleanup ifdefs Rhyland Klein
2013-02-20 19:15 ` Stephen Warren
[not found] ` <1361385317-6020-4-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-06 21:09 ` Stephen Warren
[not found] ` <5137B07C.1040700-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-06 22:54 ` Chris Ball
[not found] ` <87r4js16ml.fsf-DGHOrqG7t0YzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2013-03-06 23:17 ` Stephen Warren
[not found] ` <5137CE9B.3070203-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-06 23:47 ` Chris Ball
2013-02-20 18:35 ` [PATCH 4/4] mmc: host: sdhci-tegra: add basic support for Tegra114 Rhyland Klein
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=51252103.70202@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=praithatha@nvidia.com \
--cc=rklein@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 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).