public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add LEDs support for the ARM Versatile DT
Date: Fri, 08 Jan 2016 11:48:23 +0100	[thread overview]
Message-ID: <4424714.7WQ7ShA7WE@wuerfel> (raw)
In-Reply-To: <1452002529-3335-1-git-send-email-linus.walleij@linaro.org>

On Tuesday 05 January 2016 15:02:07 Linus Walleij wrote:
> This adds support for the board LEDs to the ARM Versatile device tree
> version.
> 
> I can't decice if this is a regression or not. The board file version
> of Versatile supported the LEDs, the Device Tree version never did
> until now.
> 
> The board file version of Versatile was deleted in
> commit 16956fed35fecde2201e23458cda193526b19559
> "ARM: versatile: switch to DT only booting and remove legacy code"
> 
> If we consider the DT version a full drop-in replacement for the
> board file version, then this should go in as a regression fix. If
> it is not, we can delay it to the next merge window.
> 
> Sending this to arm at kernel.org anyway so the ARM SoC maintainers can
> decide.
> 

It's really late, but I'd consider them sort-of fixes, and they seem
rather harmless, so I've put them in.

	Arnd

      parent reply	other threads:[~2016-01-08 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 14:02 [PATCH 0/2] Add LEDs support for the ARM Versatile DT Linus Walleij
2016-01-05 14:02 ` [PATCH 1/2] ARM: versatile: add the syscon LEDs to the DT Linus Walleij
2016-01-05 15:37   ` Rob Herring
2016-01-05 23:24     ` Linus Walleij
2016-01-08 10:47   ` Arnd Bergmann
2016-01-05 14:02 ` [PATCH 2/2] ARM: versatile: enable the right LEDs Linus Walleij
2016-01-08 10:46   ` Arnd Bergmann
2016-01-08 10:48 ` Arnd Bergmann [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=4424714.7WQ7ShA7WE@wuerfel \
    --to=arnd@arndb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox