All of lore.kernel.org
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Fix dts files w/ status property: "disable" -> "disabled"
Date: Mon, 11 Jun 2012 21:02:15 +0200	[thread overview]
Message-ID: <4FD640B7.90106@antcom.de> (raw)
In-Reply-To: <4FD62B2A.2030600@wwwdotorg.org>

On 11/06/12 19:30, Stephen Warren wrote:
> On 06/11/2012 09:11 AM, Roland Stigge wrote:
>> This patches fixes some status = "disable" strings to "disabled", the correct
>> way of disabling nodes in the devicetree.
>>
>> lpc32xx.dtsi is fixed separately in the LPC32xx patch set due to the many
>> changes there.
> 
> The Tegra parts,
> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
> 
> Are you intending this to be applied for 3.5? If so, that's fine. If
> not, splitting it up so I can take the Tegra parts through the Tegra
> tree would reduce the possibility of conflicts.

I would only put it into v3.6. Everything works fine without it (as Arnd
described), it just confused amateurs like me. :-)

Therefore, splitting it up.

Thanks,

Roland

WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, b-cousson@ti.com,
	grant.likely@secretlab.ca, rob.herring@calxeda.com
Subject: Re: [PATCH] ARM: Fix dts files w/ status property: "disable" -> "disabled"
Date: Mon, 11 Jun 2012 21:02:15 +0200	[thread overview]
Message-ID: <4FD640B7.90106@antcom.de> (raw)
In-Reply-To: <4FD62B2A.2030600@wwwdotorg.org>

On 11/06/12 19:30, Stephen Warren wrote:
> On 06/11/2012 09:11 AM, Roland Stigge wrote:
>> This patches fixes some status = "disable" strings to "disabled", the correct
>> way of disabling nodes in the devicetree.
>>
>> lpc32xx.dtsi is fixed separately in the LPC32xx patch set due to the many
>> changes there.
> 
> The Tegra parts,
> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
> 
> Are you intending this to be applied for 3.5? If so, that's fine. If
> not, splitting it up so I can take the Tegra parts through the Tegra
> tree would reduce the possibility of conflicts.

I would only put it into v3.6. Everything works fine without it (as Arnd
described), it just confused amateurs like me. :-)

Therefore, splitting it up.

Thanks,

Roland

  reply	other threads:[~2012-06-11 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 15:11 [PATCH] ARM: Fix dts files w/ status property: "disable" -> "disabled" Roland Stigge
2012-06-11 15:11 ` Roland Stigge
2012-06-11 16:24 ` Rob Herring
2012-06-11 16:24   ` Rob Herring
2012-06-11 17:30 ` Stephen Warren
2012-06-11 17:30   ` Stephen Warren
2012-06-11 19:02   ` Roland Stigge [this message]
2012-06-11 19:02     ` Roland Stigge

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=4FD640B7.90106@antcom.de \
    --to=stigge@antcom.de \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.