From: Rob Herring <robh@kernel.org>
To: "Badel, Laurent" <LaurentBadel@eaton.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"fugang.duan@nxp.com" <fugang.duan@nxp.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"m.felsch@pengutronix.de" <m.felsch@pengutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"richard.leitner@skidata.com" <richard.leitner@skidata.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Quette, Arnaud" <ArnaudQuette@Eaton.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH net 2/4] net:phy:smsc: expand documentation of clocks property
Date: Fri, 30 Oct 2020 14:19:10 -0500 [thread overview]
Message-ID: <20201030191910.GA4174476@bogus> (raw)
In-Reply-To: <CY4PR1701MB187834A07970380742371D78DF160@CY4PR1701MB1878.namprd17.prod.outlook.com>
On Tue, 27 Oct 2020 23:27:42 +0000, Badel, Laurent wrote:
> Subject: [PATCH net 2/4] net:phy:smsc: expand documentation of clocks property
>
> Description: The ref clock is managed differently when added to the DT
> entry for SMSC PHY. Thus, specify this more clearly in the documentation.
>
> Signed-off-by: Laurent Badel <laurentbadel@eaton.com>
> ---
> Documentation/devicetree/bindings/net/smsc-lan87xx.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-10-30 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 23:27 [PATCH net 2/4] net:phy:smsc: expand documentation of clocks property Badel, Laurent
2020-10-30 19:19 ` Rob Herring [this message]
2020-11-04 12:11 ` [EXTERNAL] " Badel, Laurent
2020-11-04 16:01 ` Florian Fainelli
2020-11-09 15:16 ` Badel, Laurent
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=20201030191910.GA4174476@bogus \
--to=robh@kernel.org \
--cc=ArnaudQuette@Eaton.com \
--cc=LaurentBadel@eaton.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=m.felsch@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=richard.leitner@skidata.com \
--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).