From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
michael@walle.cc
Subject: Re: [PATCH net-next v4 0/2] net: micrel: Add support for lan8841 PHY
Date: Wed, 08 Feb 2023 09:20:18 +0000 [thread overview]
Message-ID: <167584801877.16330.13349498131343728827.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230207105212.1275396-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 7 Feb 2023 11:52:10 +0100 you wrote:
> Add support for lan8841 PHY.
>
> The first patch add the support for lan8841 PHY which can run at
> 10/100/1000Mbit. It also has support for other features, but they are not
> added in this series.
>
> The second patch updates the documentation for the dt-bindings which is
> similar to the ksz9131.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] net: micrel: Add support for lan8841 PHY
https://git.kernel.org/netdev/net-next/c/a8f1a19d27ef
- [net-next,v4,2/2] dt-bindings: net: micrel-ksz90x1.txt: Update for lan8841
https://git.kernel.org/netdev/net-next/c/33e581d76e35
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-08 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:52 [PATCH net-next v4 0/2] net: micrel: Add support for lan8841 PHY Horatiu Vultur
2023-02-07 10:52 ` [PATCH net-next v4 1/2] " Horatiu Vultur
2023-02-07 13:27 ` Andrew Lunn
2023-02-07 10:52 ` [PATCH net-next v4 2/2] dt-bindings: net: micrel-ksz90x1.txt: Update for lan8841 Horatiu Vultur
2023-02-08 9:20 ` patchwork-bot+netdevbpf [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=167584801877.16330.13349498131343728827.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).