From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
DTML <devicetree@vger.kernel.org>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] add additional required properties for UniPhier ethernet nodes
Date: Wed, 25 Apr 2018 00:28:45 +0900 [thread overview]
Message-ID: <CAK7LNAT2acPfF-mK47Lu3Qc89TrFmSCppLXqSxYiX+eJ=ZKXSg@mail.gmail.com> (raw)
In-Reply-To: <1524545223-5893-1-git-send-email-hayashi.kunihiko@socionext.com>
2018-04-24 13:46 GMT+09:00 Kunihiko Hayashi <hayashi.kunihiko@socionext.com>:
> Add required clocks and their names, resets and their names, and system
> controller properties to fix the activation issues for the ethernet
> controllers implemented on some UniPhier SoCs.
>
> Kunihiko Hayashi (4):
> ARM: dts: uniphier: add required clocks and resets to Pro4 ethernet
> node
> arm64: dts: uniphier: add clock-names and reset-names to ethernet node
> ARM: dts: uniphier: add syscon-phy-mode property to each ethernet node
> arm64: dts: uniphier: add syscon-phy-mode property to each ethernet
> node
All applied to linux-uniphier. Thanks!
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2018-04-24 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 4:46 [PATCH 0/4] add additional required properties for UniPhier ethernet nodes Kunihiko Hayashi
2018-04-24 4:47 ` [PATCH 1/4] ARM: dts: uniphier: add required clocks and resets to Pro4 ethernet node Kunihiko Hayashi
2018-04-24 4:47 ` [PATCH 2/4] arm64: dts: uniphier: add clock-names and reset-names to " Kunihiko Hayashi
2018-04-24 4:47 ` [PATCH 3/4] ARM: dts: uniphier: add syscon-phy-mode property to each " Kunihiko Hayashi
2018-04-24 4:47 ` [PATCH 4/4] arm64: " Kunihiko Hayashi
2018-04-24 15:28 ` Masahiro Yamada [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='CAK7LNAT2acPfF-mK47Lu3Qc89TrFmSCppLXqSxYiX+eJ=ZKXSg@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=robh+dt@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).