From: Michael Walle <michael@walle.cc>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
lgirdwood@gmail.com, broonie@kernel.org,
simon.horman@netronome.com
Subject: Re: [PATCH 0/5] net: phy: at803x device tree binding
Date: Tue, 05 Nov 2019 23:22:51 +0100 [thread overview]
Message-ID: <0265fc6d0d0eb64f578959a8883295bd@walle.cc> (raw)
In-Reply-To: <20191105.140616.1174888253359674234.davem@davemloft.net>
Am 2019-11-05 23:06, schrieb David Miller:
> From: Michael Walle <michael@walle.cc>
> Date: Sat, 2 Nov 2019 02:13:46 +0100
>
>> Adds a device tree binding to configure the clock and the RGMII
>> voltage.
>
> This does not apply cleanly to net-next, please respin.
That is actually just fine, because there is a bug in the AR8035
handling. I'll fix that and rebase it on your net-next.
Thanks,
-michael
prev parent reply other threads:[~2019-11-05 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 1:13 [PATCH 0/5] net: phy: at803x device tree binding Michael Walle
2019-11-02 1:13 ` [PATCH 1/5] net: phy: at803x: fix Kconfig description Michael Walle
2019-11-02 2:57 ` Florian Fainelli
2019-11-02 1:13 ` [PATCH 2/5] dt-bindings: net: phy: Add support for AT803X Michael Walle
2019-11-02 2:59 ` Florian Fainelli
2019-11-06 4:37 ` Rob Herring
2019-11-02 1:13 ` [PATCH 3/5] net: phy: at803x: add device tree binding Michael Walle
2019-11-02 3:01 ` Florian Fainelli
2019-11-05 22:28 ` Michael Walle
2019-11-02 1:13 ` [PATCH 4/5] net: phy: at803x: mention AR8033 as same as AR8031 Michael Walle
2019-11-02 1:13 ` [PATCH 5/5] net: phy: at803x: fix the PHY names Michael Walle
2019-11-02 3:21 ` Florian Fainelli
2019-11-05 22:06 ` [PATCH 0/5] net: phy: at803x device tree binding David Miller
2019-11-05 22:22 ` Michael Walle [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=0265fc6d0d0eb64f578959a8883295bd@walle.cc \
--to=michael@walle.cc \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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 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).