From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, rmk+kernel@armlinux.org.uk,
andrew@lunn.ch, hkallweit1@gmail.com
Subject: Re: [PATCH net-next v2 1/2] net: sfp: update comment for FS SFP-10G-T quirk
Date: Fri, 26 Apr 2024 02:00:28 +0000 [thread overview]
Message-ID: <171409682823.30663.5163968269339844749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423085039.26957-1-kabel@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 23 Apr 2024 10:50:38 +0200 you wrote:
> Update the comment for the Fibrestore SFP-10G-T module: since commit
> e9301af385e7 ("net: sfp: fix PHY discovery for FS SFP-10G-T module")
> we also do a 4 second wait before probing the PHY.
>
> Fixes: e9301af385e7 ("net: sfp: fix PHY discovery for FS SFP-10G-T module")
> Signed-off-by: Marek Behún <kabel@kernel.org>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: sfp: update comment for FS SFP-10G-T quirk
https://git.kernel.org/netdev/net-next/c/6999e0fc9a55
- [net-next,v2,2/2] net: sfp: enhance quirk for Fibrestore 2.5G copper SFP module
https://git.kernel.org/netdev/net-next/c/cd4a32e60061
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-04-26 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 8:50 [PATCH net-next v2 1/2] net: sfp: update comment for FS SFP-10G-T quirk Marek Behún
2024-04-23 8:50 ` [PATCH net-next v2 2/2] net: sfp: enhance quirk for Fibrestore 2.5G copper SFP module Marek Behún
2024-04-23 11:41 ` Jiri Pirko
2024-04-23 11:45 ` Marek Behún
2024-04-23 11:39 ` [PATCH net-next v2 1/2] net: sfp: update comment for FS SFP-10G-T quirk Jiri Pirko
2024-04-26 2:00 ` 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=171409682823.30663.5163968269339844749.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.