From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@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, wojciech.drewek@intel.com,
arun.ramadoss@microchip.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v3 0/2] net: phy: micrel: lan8814 erratas
Date: Tue, 05 Mar 2024 19:20:31 +0000 [thread overview]
Message-ID: <170966643127.28029.9572611359773459427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304091548.1386022-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 4 Mar 2024 10:15:46 +0100 you wrote:
> Add two erratas for lan8814. First one fix the led which might
> stay on even that there is no link. The second one improves increases
> length of the cable that can be used when used in 1000Base-T.
>
> v2->v3:
> - drop trailing underscore from register definitions
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: phy: micrel: lan8814 led errata
https://git.kernel.org/netdev/net-next/c/e9097f8e1e76
- [net-next,v3,2/2] net: phy: micrel: lan8814 cable improvement errata
https://git.kernel.org/netdev/net-next/c/ad080db4483b
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:[~2024-03-05 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 9:15 Horatiu Vultur
2024-03-04 9:15 ` [PATCH net-next v3 1/2] net: phy: micrel: lan8814 led errata Horatiu Vultur
2024-03-04 13:24 ` Andrew Lunn
2024-03-04 9:15 ` [PATCH net-next v3 2/2] net: phy: micrel: lan8814 cable improvement errata Horatiu Vultur
2024-03-04 13:25 ` Andrew Lunn
2024-03-04 14:08 ` Arun.Ramadoss
2024-03-05 19: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=170966643127.28029.9572611359773459427.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--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=wojciech.drewek@intel.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
all inboxes | Powered by JetHome®