public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@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 14:22:53 -0500	[thread overview]
Message-ID: <87ppzwglbm.fsf@octavius.laptop.org> (raw)
In-Reply-To: <5123CFB9.7020209-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> (Stephen Warren's message of "Tue, 19 Feb 2013 12:17:13 -0700")

Hi Stephen,

On Tue, Feb 19 2013, Stephen Warren wrote:
>> 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.

I'll take it for 3.9 (perhaps straight after -rc1), since this is a more
of a cleanup than a new feature.  I've pushed it to mmc-next now so that
testing can happen in the meantime.

Thanks,

- Chris.
-- 
Chris Ball   <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>   <http://printf.net/>
One Laptop Per Child

      parent reply	other threads:[~2013-02-19 19:22 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
     [not found]     ` <5123CFB9.7020209-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-19 19:22       ` Chris Ball [this message]

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=87ppzwglbm.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=swarren-3lzwWm7+Weoh9ZMKESR00Q@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