From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: DT: Kirkwood: Use symbolic names from input.h
Date: Tue, 03 Dec 2013 21:39:02 +0100 [thread overview]
Message-ID: <87fvq9brfd.fsf@natisbad.org> (raw)
In-Reply-To: <1386100305-31280-1-git-send-email-andrew@lunn.ch> (Andrew Lunn's message of "Tue, 3 Dec 2013 20:51:44 +0100")
Hi Andrew,
Andrew Lunn <andrew@lunn.ch> writes:
> Replace the numeric key value with a symbolic name from
> <bt-bindings/input/input.h>
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> arch/arm/boot/dts/kirkwood-cloudbox.dts | 2 +-
> arch/arm/boot/dts/kirkwood-dnskw.dtsi | 6 +++---
> arch/arm/boot/dts/kirkwood-ib62x0.dts | 4 ++--
> arch/arm/boot/dts/kirkwood-iconnect.dts | 4 ++--
> arch/arm/boot/dts/kirkwood-iomega_ix2_200.dts | 6 +++---
> arch/arm/boot/dts/kirkwood-lsxl.dtsi | 6 +++---
> arch/arm/boot/dts/kirkwood-mv88f6281gtw-ge.dts | 4 ++--
> arch/arm/boot/dts/kirkwood-netgear_readynas_duo_v2.dts | 6 +++---
Jason just applied (yesterday IIRC) to mvebu/dt a series which provides
cleanup for ReadyNAS .dts files. Among other things, it replaces numeric
key values with a symbolic name. And it also does the same for GPIO
voltage level. I guess you can remove that specific .dts from your patch.
Just in case you have the same in preparation for armada .dts files,
RN102 and RN104 .dts files are also fixed in mvebu/dt.
Anyway, thanks for that work.
Cheers,
a+
next prev parent reply other threads:[~2013-12-03 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 19:51 [PATCH 1/2] ARM: DT: Kirkwood: Use symbolic names from input.h Andrew Lunn
2013-12-03 19:51 ` [PATCH 2/2] ARM: DT: Kirkwood: Use symbolic names from gpio.h Andrew Lunn
2013-12-03 20:39 ` Arnaud Ebalard [this message]
2013-12-03 21:14 ` [PATCH 1/2] ARM: DT: Kirkwood: Use symbolic names from input.h Jason Cooper
2013-12-03 21:50 ` Andrew Lunn
2013-12-03 21:56 ` Jason Cooper
2013-12-03 22:28 ` Andrew Lunn
2013-12-04 5:21 ` Jason Cooper
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=87fvq9brfd.fsf@natisbad.org \
--to=arno@natisbad.org \
--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.