From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, daniel@makrotopia.org, kabel@kernel.org
Subject: Re: [PATCH net-next 0/7] net: sfp: add support for control of rate selection
Date: Fri, 19 May 2023 03:00:21 +0000 [thread overview]
Message-ID: <168446522165.19635.8763105923097917557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZGSuTY8GqjM+sqta@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 17 May 2023 11:37:01 +0100 you wrote:
> Hi,
>
> This series introduces control of the rate selection SFP pins (or
> their soft state in the I2C diagnostics EEPROM). Several SNIA documents
> (referenced in the commits) describe the various different modes for
> these, and we implement them all for maximum compatibility, but as
> we know, SFP modules tend to do their own thing, so that may not be
> sufficient.
>
> [...]
Here is the summary with links:
- [net-next,1/7] net: sfp: add helper to modify signal states
https://git.kernel.org/netdev/net-next/c/418c1214741c
- [net-next,2/7] net: sfp: move rtnl lock to cover reading state
https://git.kernel.org/netdev/net-next/c/d47e5a430dfd
- [net-next,3/7] net: sfp: swap order of rtnl and st_mutex locks
https://git.kernel.org/netdev/net-next/c/a9fe964e7aae
- [net-next,4/7] net: sfp: move sm_mutex into sfp_check_state()
https://git.kernel.org/netdev/net-next/c/97a492050aa5
- [net-next,5/7] net: sfp: change st_mutex locking
https://git.kernel.org/netdev/net-next/c/1974fd3bf0f0
- [net-next,6/7] net: sfp: add support for setting signalling rate
https://git.kernel.org/netdev/net-next/c/dc18582211b3
- [net-next,7/7] net: sfp: add support for rate selection
https://git.kernel.org/netdev/net-next/c/fc082b39d0a2
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-05-19 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 10:37 [PATCH net-next 0/7] net: sfp: add support for control of rate selection Russell King (Oracle)
2023-05-17 10:37 ` [PATCH net-next 1/7] net: sfp: add helper to modify signal states Russell King (Oracle)
2023-05-17 10:37 ` [PATCH net-next 2/7] net: sfp: move rtnl lock to cover reading state Russell King (Oracle)
2023-05-17 10:37 ` [PATCH net-next 3/7] net: sfp: swap order of rtnl and st_mutex locks Russell King (Oracle)
2023-05-17 10:38 ` [PATCH net-next 4/7] net: sfp: move sm_mutex into sfp_check_state() Russell King (Oracle)
2023-05-17 10:38 ` [PATCH net-next 5/7] net: sfp: change st_mutex locking Russell King (Oracle)
2023-05-17 10:38 ` [PATCH net-next 6/7] net: sfp: add support for setting signalling rate Russell King (Oracle)
2023-05-17 10:38 ` [PATCH net-next 7/7] net: sfp: add support for rate selection Russell King (Oracle)
2023-05-17 15:52 ` Andrew Lunn
2023-05-19 3: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=168446522165.19635.8763105923097917557.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kabel@kernel.org \
--cc=kuba@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 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.