From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
mlxsw@nvidia.com, idosch@nvidia.com
Subject: Re: [patch net-next 0/3] mlx*: devlink dev info versions adjustments
Date: Thu, 27 May 2021 22:00:03 +0000 [thread overview]
Message-ID: <162215280350.25428.11680179973826185726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210526104509.761807-1-jiri@resnulli.us>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 26 May 2021 12:45:06 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Couple of adjustments in Mellanox drivers regarding devlink dev
> versions fill-up.
>
> Jiri Pirko (3):
> net/mlx5: Expose FW version over defined keyword
> mlxsw: core: Expose FW version over defined keyword
> mlxsw: core: use PSID string define in devlink info
>
> [...]
Here is the summary with links:
- [net-next,1/3] net/mlx5: Expose FW version over defined keyword
https://git.kernel.org/netdev/net-next/c/2754125ebd33
- [net-next,2/3] mlxsw: core: Expose FW version over defined keyword
https://git.kernel.org/netdev/net-next/c/f55c998c274e
- [net-next,3/3] mlxsw: core: use PSID string define in devlink info
https://git.kernel.org/netdev/net-next/c/7dafcc4c9dfb
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-05-27 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 10:45 [patch net-next 0/3] mlx*: devlink dev info versions adjustments Jiri Pirko
2021-05-26 10:45 ` [patch net-next 1/3] net/mlx5: Expose FW version over defined keyword Jiri Pirko
2021-05-27 22:10 ` Saeed Mahameed
2021-05-26 10:45 ` [patch net-next 2/3] mlxsw: core: " Jiri Pirko
2021-05-26 10:45 ` [patch net-next 3/3] mlxsw: core: use PSID string define in devlink info Jiri Pirko
2021-05-27 22: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=162215280350.25428.11680179973826185726.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
/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.