From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, kuba@kernel.org, davem@davemloft.net,
linux@armlinux.org.uk, hkallweit1@gmail.com, andrew@lunn.ch,
UNGLinuxDriver@microchip.com
Subject: Re: [Patch net-next v3 0/2] add ethtool SQI support for LAN87xx T1 Phy
Date: Fri, 22 Apr 2022 23:40:11 +0000 [thread overview]
Message-ID: <165067081195.10261.5864387127941865463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220420152016.9680-1-arun.ramadoss@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 Apr 2022 20:50:14 +0530 you wrote:
> This patch series add the Signal Quality Index measurement for the LAN87xx and
> LAN937x T1 phy. Updated the maintainers file for microchip_t1.c.
>
> v2 - v3
> ------
> Rebased to latest commit
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: phy: LAN87xx: add ethtool SQI support
https://git.kernel.org/netdev/net-next/c/b649695248b1
- [net-next,v3,2/2] MAINTAINERS: Add maintainers for Microchip T1 Phy driver
https://git.kernel.org/netdev/net-next/c/58f373f8d787
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-04-22 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 15:20 [Patch net-next v3 0/2] add ethtool SQI support for LAN87xx T1 Phy Arun Ramadoss
2022-04-20 15:20 ` [Patch net-next v3 1/2] net: phy: LAN87xx: add ethtool SQI support Arun Ramadoss
2022-04-20 15:20 ` [Patch net-next v3 2/2] MAINTAINERS: Add maintainers for Microchip T1 Phy driver Arun Ramadoss
2022-04-22 23: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=165067081195.10261.5864387127941865463.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=hkallweit1@gmail.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 \
/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