From: patchwork-bot+netdevbpf@kernel.org
To: Louis Peens <louis.peens@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
jiri@resnulli.us, fei.qin@corigine.com, netdev@vger.kernel.org,
oss-drivers@corigine.com
Subject: Re: [PATCH net-next v5 0/2] nfp: series of minor driver improvements
Date: Fri, 12 Apr 2024 10:50:30 +0000 [thread overview]
Message-ID: <171291903021.14580.4622607080457516471.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240410112636.18905-1-louis.peens@corigine.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 10 Apr 2024 13:26:34 +0200 you wrote:
> This short series bundles now only includes a small update to add a
> board part number to devlink. Previously some dim patches also formed
> part of this series, these were dropped in v5.
>
> Patch1: Add new define for devlink string "board.part_number"
> Patch2: Make use of this field in the nfp driver
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] devlink: add a new info version tag
https://git.kernel.org/netdev/net-next/c/3bb946c9d323
- [net-next,v5,2/2] nfp: update devlink device info output
https://git.kernel.org/netdev/net-next/c/8910f93b9570
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-12 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 11:26 [PATCH net-next v5 0/2] nfp: series of minor driver improvements Louis Peens
2024-04-10 11:26 ` [PATCH net-next v5 1/2] devlink: add a new info version tag Louis Peens
2024-04-10 11:26 ` [PATCH net-next v5 2/2] nfp: update devlink device info output Louis Peens
2024-04-10 22:27 ` Jacob Keller
2024-04-11 6:18 ` Louis Peens
2024-04-11 16:10 ` Keller, Jacob E
2024-04-12 10:50 ` 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=171291903021.14580.4622607080457516471.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=fei.qin@corigine.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--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.