From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b
Date: Fri, 18 Mar 2016 18:36:44 +0100 [thread overview]
Message-ID: <56EC3CAC.6040904@suse.de> (raw)
In-Reply-To: <1456869876-19320-4-git-send-email-carlo@caione.org>
Am 01.03.2016 um 23:04 schrieb Carlo Caione:
> From: Carlo Caione <carlo@endlessm.com>
>
> Signed-off-by: Carlo Caione <carlo@endlessm.com>
> ---
> arch/arm/boot/dts/meson8.dtsi | 57 ++++++++++++++++++++++++------------------
> arch/arm/boot/dts/meson8b.dtsi | 12 +++++++--
> 2 files changed, 42 insertions(+), 27 deletions(-)
Looks sane to me,
Reviewed-by: Andreas F?rber <afaerber@suse.de>
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-03-18 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 22:04 [PATCH 0/4] Refactor pinctrl driver for aobus / cbus Carlo Caione
2016-03-01 22:04 ` [PATCH 1/4] pinctrl: amlogic: Separate some pin functions for Meson8 / Meson8b Carlo Caione
2016-03-09 5:59 ` Linus Walleij
2016-03-01 22:04 ` [PATCH 2/4] pinctrl: amlogic: Make driver independent from two-domain configuration Carlo Caione
2016-03-09 6:01 ` Linus Walleij
2016-03-17 3:31 ` Kevin Hilman
2016-03-17 4:28 ` Kevin Hilman
2016-03-17 7:09 ` Carlo Caione
2016-03-17 15:35 ` Kevin Hilman
2016-03-17 18:15 ` Carlo Caione
2016-03-18 16:14 ` Kevin Hilman
2016-03-01 22:04 ` [PATCH 3/4] ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b Carlo Caione
2016-03-18 17:36 ` Andreas Färber [this message]
2016-03-01 22:04 ` [PATCH 4/4] documentation: Fix pinctrl documentation " Carlo Caione
2016-03-05 4:26 ` Rob Herring
2016-03-07 9:01 ` Carlo Caione
2016-03-09 9:41 ` [PATCH v2 " Carlo Caione
2016-03-15 9:10 ` Linus Walleij
2016-03-15 9:20 ` Carlo Caione
2016-03-18 16:59 ` Kevin Hilman
2016-03-18 17:45 ` Andreas Färber
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=56EC3CAC.6040904@suse.de \
--to=afaerber@suse.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;
as well as URLs for NNTP newsgroup(s).