From: Neil Armstrong <narmstrong@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Christian Hewitt <christianshewitt@gmail.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Igor Vavro <afl2001@gmail.com>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] pinctrl: meson: add tsin pinctrl for meson gxbb/gxl/gxm
Date: Wed, 4 Mar 2020 11:03:29 +0100 [thread overview]
Message-ID: <999512c9-e50b-af51-7875-7fe9fca665de@baylibre.com> (raw)
In-Reply-To: <CACRpkdZ4+-26Q01nx9iFJLUSCfM0Cuh6U8=gdtP=63xMd+2jqA@mail.gmail.com>
Hi,
On 03/03/2020 13:40, Linus Walleij wrote:
> On Mon, Mar 2, 2020 at 5:41 AM Christian Hewitt
> <christianshewitt@gmail.com> wrote:
>
>> From: Igor Vavro <afl2001@gmail.com>
>>
>> Add the tsin pinctrl definitions needed for integrated DVB hardware
>> support on Meson GXBB/GXL/GXM boards.
>>
>> Signed-off-by: Igor Vavro <afl2001@gmail.com>
>> [updated commit message]
>> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
>
> Can I get Martin and/or Neil to review this?
Otto replied on linux-amlogic only, reporting an issue with the path, also
modifying the uart_c pin registers bits.
So it needs a resend.
Neil
>
> Yours,
> Linus Walleij
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-03-04 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 4:40 Christian Hewitt
2020-03-03 12:40 ` Linus Walleij
2020-03-04 10:03 ` Neil Armstrong [this message]
2020-03-03 13:23 Otto Meier
2020-03-03 14:05 ` Neil Armstrong
2020-03-04 9:27 ` Kevin Hilman
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=999512c9-e50b-af51-7875-7fe9fca665de@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=afl2001@gmail.com \
--cc=christianshewitt@gmail.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
/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
all inboxes | Powered by JetHome®