public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
Cc: linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] mmc: tegra: assume CONFIG_OF, remove platform data
Date: Tue, 19 Feb 2013 12:17:13 -0700	[thread overview]
Message-ID: <5123CFB9.7020209@wwwdotorg.org> (raw)
In-Reply-To: <1360966039-24071-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On 02/15/2013 03:07 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> 
> Tegra only supports, and always enables, device tree. Remove all ifdefs
> and runtime checks for DT support from the driver. Platform data is
> therefore no longer required. Rework the driver to parse the device tree
> directly into struct sdhci_tegra.

Chris,

If you can take this for 3.9, everything is simple. I understand it's
very late for that.

If this goes into 3.10, then there will be some dependencies. Can you
ack this patch so that I can take it through the Tegra tree? The reason
being: I know that Joseph Lo will be posting some patches to this file
that need to go through the Tegra tree due to device tree dependencies,
and the simplest way to resolve it is just to take all changes to this
file through the Tegra tree in 3.10. Thanks.

  parent reply	other threads:[~2013-02-19 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 22:07 [PATCH] mmc: tegra: assume CONFIG_OF, remove platform data Stephen Warren
     [not found] ` <1360966039-24071-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-19 19:17   ` Stephen Warren [this message]
     [not found]     ` <5123CFB9.7020209-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-19 19:22       ` 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=5123CFB9.7020209@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org \
    --cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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