From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
andrew@lunn.ch, mkubecek@suse.cz, pali@kernel.org,
jacob.e.keller@intel.com, jiri@nvidia.com, vadimp@nvidia.com,
mlxsw@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH net-next v2 0/6] ethtool: Add ability to control transceiver modules' power mode
Date: Thu, 07 Oct 2021 01:10:08 +0000 [thread overview]
Message-ID: <163356900850.5781.2836466708298272842.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211006104647.2357115-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 6 Oct 2021 13:46:41 +0300 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> This patchset extends the ethtool netlink API to allow user space to
> control transceiver modules. Two specific APIs are added, but the plan
> is to extend the interface with more APIs in the future (see "Future
> plans").
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] ethtool: Add ability to control transceiver modules' power mode
applied by Jakub Kicinski <kuba@kernel.org>
https://git.kernel.org/netdev/net-next/c/353407d917b2
- [net-next,v2,2/6] mlxsw: reg: Add Port Module Memory Map Properties register
applied by Jakub Kicinski <kuba@kernel.org>
https://git.kernel.org/netdev/net-next/c/f10ba086f7e3
- [net-next,v2,3/6] mlxsw: reg: Add Management Cable IO and Notifications register
applied by Jakub Kicinski <kuba@kernel.org>
https://git.kernel.org/netdev/net-next/c/fc53f5fb8037
- [net-next,v2,4/6] mlxsw: Add ability to control transceiver modules' power mode
applied by Jakub Kicinski <kuba@kernel.org>
https://git.kernel.org/netdev/net-next/c/0455dc50bcca
- [net-next,v2,5/6] ethtool: Add transceiver module extended state
applied by Jakub Kicinski <kuba@kernel.org>
https://git.kernel.org/netdev/net-next/c/3dfb51126064
- [net-next,v2,6/6] mlxsw: Add support for transceiver module extended state
applied by Jakub Kicinski <kuba@kernel.org>
https://git.kernel.org/netdev/net-next/c/235dbbec7d72
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:[~2021-10-07 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 10:46 [PATCH net-next v2 0/6] ethtool: Add ability to control transceiver modules' power mode Ido Schimmel
2021-10-06 10:46 ` [PATCH net-next v2 1/6] " Ido Schimmel
2021-10-06 10:46 ` [PATCH net-next v2 2/6] mlxsw: reg: Add Port Module Memory Map Properties register Ido Schimmel
2021-10-06 10:46 ` [PATCH net-next v2 3/6] mlxsw: reg: Add Management Cable IO and Notifications register Ido Schimmel
2021-10-06 10:46 ` [PATCH net-next v2 4/6] mlxsw: Add ability to control transceiver modules' power mode Ido Schimmel
2021-10-06 10:46 ` [PATCH net-next v2 5/6] ethtool: Add transceiver module extended state Ido Schimmel
2021-10-06 10:46 ` [PATCH net-next v2 6/6] mlxsw: Add support for " Ido Schimmel
2021-10-07 1:10 ` 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=163356900850.5781.2836466708298272842.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pali@kernel.org \
--cc=vadimp@nvidia.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.