From: Stephen Boyd <sboyd@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>
Cc: devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH net-next v2 2/3] net: phy: add amlogic g12a mdio mux support
Date: Fri, 29 Mar 2019 15:49:06 -0700 [thread overview]
Message-ID: <155389974643.20095.8059052762611235333@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190329141512.29867-3-jbrunet@baylibre.com>
Quoting Jerome Brunet (2019-03-29 07:15:11)
> Add support for the mdio mux and internal phy glue of the g12a SoC family
>
> [for the clock part]
> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
I think you should write it like:
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com> # clk parts
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-03-29 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 14:15 [PATCH net-next v2 0/3] net: phy: add Amlogic g12a support Jerome Brunet
2019-03-29 14:15 ` [PATCH net-next v2 1/3] dt-bindings: net: phy: add g12a mdio mux documentation Jerome Brunet
2019-03-29 14:15 ` [PATCH net-next v2 2/3] net: phy: add amlogic g12a mdio mux support Jerome Brunet
2019-03-29 22:49 ` Stephen Boyd [this message]
2019-03-29 14:15 ` [PATCH net-next v2 3/3] net: phy: meson-gxl: add g12a support Jerome Brunet
2019-03-29 19:22 ` Heiner Kallweit
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=155389974643.20095.8059052762611235333@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=netdev@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
all inboxes | Powered by JetHome®