From: Neil Armstrong <narmstrong@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] pinctrl: meson-gxl: Add Ethernet PHY LEDS pins
Date: Mon, 29 May 2017 11:17:09 +0200 [thread overview]
Message-ID: <a0f0bf3e-a23c-eec2-03a0-a6c35125028f@baylibre.com> (raw)
In-Reply-To: <CACRpkdY6rwx=Z2YZRA=DUjvRDe6cCc7cyFrdb3JbiisHVK+kCQ@mail.gmail.com>
On 05/29/2017 11:01 AM, Linus Walleij wrote:
> On Wed, May 24, 2017 at 10:20 AM, Neil Armstrong
> <narmstrong@baylibre.com> wrote:
>
>> The Amlogic Meson GXL SoCs embeds an 10/100 Ethernet PHY, this patchs enables
>> the Link and Activity LEDs signals.
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>
> Patch applied with Jerome's review tag.
>
> Yours,
> Linus Walleij
>
Thanks Linus !
Neil
prev parent reply other threads:[~2017-05-29 9:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 8:20 [PATCH 0/5] pinctrl: meson: new pins and fixes round 2 Neil Armstrong
2017-05-24 8:20 ` [PATCH 1/5] pinctrl: meson-gxl: Fix typo in AO I2S pins Neil Armstrong
2017-05-24 8:41 ` Jerome Brunet
2017-05-29 8:57 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 2/5] pinctrl: meson-gxl: Fix typo in AO SPDIF pins Neil Armstrong
2017-05-24 8:42 ` Jerome Brunet
2017-05-29 8:58 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 3/5] pinctrl: meson-gxbb: Add CEC pins Neil Armstrong
2017-05-24 8:53 ` Jerome Brunet
2017-05-29 8:59 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 4/5] pinctrl: meson-gxl: " Neil Armstrong
2017-05-24 8:54 ` Jerome Brunet
2017-05-29 9:00 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 5/5] pinctrl: meson-gxl: Add Ethernet PHY LEDS pins Neil Armstrong
2017-05-24 8:57 ` Jerome Brunet
2017-05-29 9:01 ` Linus Walleij
2017-05-29 9:17 ` Neil Armstrong [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=a0f0bf3e-a23c-eec2-03a0-a6c35125028f@baylibre.com \
--to=narmstrong@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 \
/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).