From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <michael@walle.cc>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, Rob Herring <robh@kernel.org>,
David Miller <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Simon Horman <simon.horman@netronome.com>,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH v2 1/6] net: phy: at803x: fix Kconfig description
Date: Thu, 7 Nov 2019 02:50:03 +0100 [thread overview]
Message-ID: <20191107015003.GB8978@lunn.ch> (raw)
In-Reply-To: <20191106223617.1655-2-michael@walle.cc>
On Wed, Nov 06, 2019 at 11:36:12PM +0100, Michael Walle wrote:
> The name of the PHY is actually AR803x not AT803x. Additionally, add the
> name of the vendor and mention the AR8031 support.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2019-11-07 1:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 22:36 [PATCH v2 0/6] net: phy: at803x device tree binding Michael Walle
2019-11-06 22:36 ` [PATCH v2 1/6] net: phy: at803x: fix Kconfig description Michael Walle
2019-11-07 1:50 ` Andrew Lunn [this message]
2019-11-06 22:36 ` [PATCH v2 2/6] dt-bindings: net: phy: Add support for AT803X Michael Walle
2019-11-07 1:51 ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 3/6] net: phy: at803x: add device tree binding Michael Walle
2019-11-06 22:36 ` [PATCH v2 4/6] net: phy: at803x: mention AR8033 as same as AR8031 Michael Walle
2019-11-07 2:04 ` Andrew Lunn
2019-11-07 7:47 ` Michael Walle
2019-11-07 12:55 ` Andrew Lunn
2019-11-07 14:28 ` Michael Walle
2019-11-06 22:36 ` [PATCH v2 5/6] net: phy: at803x: fix the PHY names Michael Walle
2019-11-07 2:05 ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 6/6] net: phy: at803x: remove config_init for AR9331 Michael Walle
2019-11-07 2:05 ` Andrew Lunn
2019-11-07 5:42 ` [PATCH v2 0/6] net: phy: at803x device tree binding David Miller
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=20191107015003.GB8978@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=simon.horman@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.