public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [GIT PULL] ARM: tegra: dt2 branch
Date: Tue, 15 May 2012 10:15:43 -0600	[thread overview]
Message-ID: <4FB2812F.1010500@wwwdotorg.org> (raw)
In-Reply-To: <201205151143.26008.arnd-r2nGTMty4D4@public.gmane.org>

On 05/15/2012 05:43 AM, Arnd Bergmann wrote:
> On Monday 14 May 2012, Stephen Warren wrote:
>> I wonder if the changes to tegra-*.dtsi shouldn't just be dropped? I'd
>> personally err on the side of requiring board files to add this
>> property, rather than having things accidentally work because the .dtsi
>> file included a default.
> 
> I ended up redoing the merge because I found an embarrasing typo in my patch
> and now dropped the property for the dtsi files.
> 
>> BTW, I assume that in 3.6, I should plan to remove the support-8bit
>> properties and associated Tegra SDHCI driver code that handles them, and
>> rely on the SDHCI core handling this from now on?
> 
> I think we can't drop it from the driver because of existing powerpc machines
> providing the property, but it would be ok if you drop it from your .dts
> files.

support-8bit is parsed by the Tegra driver only, and only appears in
tegra-*.dts across all arch/*/boot.dts. I assume you were talking about
some other property, although I can't tell which from a very quick look
at arch/powerpc/boot/dts/*.

  parent reply	other threads:[~2012-05-15 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 17:20 [GIT PULL] ARM: tegra: dt2 branch Stephen Warren
     [not found] ` <1337016017-30537-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-14 17:20   ` [GIT PULL] ARM: tegra: defconfig2 branch Stephen Warren
     [not found]     ` <1337016017-30537-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-14 18:56       ` Arnd Bergmann
2012-05-14 18:54   ` [GIT PULL] ARM: tegra: dt2 branch Arnd Bergmann
     [not found]     ` <201205141854.34331.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-14 19:04       ` Stephen Warren
     [not found]         ` <4FB1572D.90500-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-14 20:37           ` Arnd Bergmann
     [not found]             ` <201205142037.08752.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-14 20:54               ` Stephen Warren
     [not found]                 ` <4FB170F3.8080107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-15 11:43                   ` Arnd Bergmann
     [not found]                     ` <201205151143.26008.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-15 16:15                       ` Stephen Warren [this message]
     [not found]                         ` <4FB2812F.1010500-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-15 19:15                           ` Arnd Bergmann
     [not found]                             ` <201205151915.25543.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-15 19:24                               ` 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=4FB2812F.1010500@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@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