From: patchwork-bot+netdevbpf@kernel.org
To: Divya Koppera <Divya.Koppera@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
UNGLinuxDriver@microchip.com, Madhuri.Sripada@microchip.com
Subject: Re: [PATCH v3 net-next 0/2] LED feature for LAN8814 PHY
Date: Sat, 02 Jul 2022 15:40:15 +0000 [thread overview]
Message-ID: <165677641578.21073.12338044854011096354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220701035709.10829-1-Divya.Koppera@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 1 Jul 2022 09:27:07 +0530 you wrote:
> Enable LED mode configuration for LAN8814 PHY
>
> v2 -> v3:
> - Fixed compilation issues
>
> v1 -> v2:
> - Updated dt-bindings for micrel,led-mode in LAN8814 PHY
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] dt-bindings: net: Updated micrel,led-mode for LAN8814 PHY
https://git.kernel.org/netdev/net-next/c/eb566fc83920
- [v3,net-next,2/2] net: phy: micrel: Adding LED feature for LAN8814 PHY
https://git.kernel.org/netdev/net-next/c/a516b7f7ca53
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:[~2022-07-02 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 3:57 Divya Koppera
2022-07-01 3:57 ` [PATCH v3 net-next 1/2] dt-bindings: net: Updated micrel,led-mode " Divya Koppera
2022-07-01 20:21 ` Rob Herring
2022-07-01 3:57 ` [PATCH v3 net-next 2/2] net: phy: micrel: Adding LED feature " Divya Koppera
2022-07-02 15:40 ` 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=165677641578.21073.12338044854011096354.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Divya.Koppera@microchip.com \
--cc=Madhuri.Sripada@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®