From: Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Rhyland Klein <rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Pritesh Raithatha
<praithatha-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 3/4] mmc: host: sdhci-tegra: cleanup ifdefs
Date: Wed, 06 Mar 2013 17:54:42 -0500 [thread overview]
Message-ID: <87r4js16ml.fsf@octavius.laptop.org> (raw)
In-Reply-To: <5137B07C.1040700-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> (Stephen Warren's message of "Wed, 06 Mar 2013 14:09:16 -0700")
Hi,
On Wed, Mar 06 2013, Stephen Warren wrote:
> On 02/20/2013 11:35 AM, Rhyland Klein wrote:
>> The structs wrapped with the SOC ifdefs are small enough where having
>> them always there shouldn't be a big overhead. Removing the ifdefs
>> also makes the code a little cleaner.
>
> I think patches 3 and 4 of this series can go through either the MMC
> tree (I checked there are no conflicts with the MMC patch I have to take
> through the Tegra tree), or the Tegra tree (since I'm taking another
> Tegra MMC patch though there), both without any dependency issues.
>
> It's your call. Let me know if you want me to take them through the
> Tegra tree with an ack. Or, if you want to take them through the MMC
> tree that's fine too. If you need them reposted to see the content, let
> me know, or they're at:
Via the MMC tree with an ack sounds good, just for the mundane reason
that I like my "highlights for 3.10" pull request to Linus to mention
when support for new MMC hardware is added, and it won't do that if
the tegra110 patch is coming through your tree.
Thanks,
- Chris.
--
Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2013-03-06 22:54 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
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 [this message]
[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=87r4js16ml.fsf@octavius.laptop.org \
--to=cjb-2x9k7bc8m7mdnm+yrofe0a@public.gmane.org \
--cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=praithatha-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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;
as well as URLs for NNTP newsgroup(s).