From: patchwork-bot+netdevbpf@kernel•org
To: Jiri Pirko <jiri@resnulli•us>
Cc: netdev@vger•kernel.org, sthemmin@microsoft•com,
dsahern@gmail•com, vikas.gupta@broadcom•com,
jacob.e.keller@intel•com, kuba@kernel•org, moshe@nvidia•com,
saeedm@nvidia•com
Subject: Re: [patch iproute2-next 0/2] devlink: allow parallel commands
Date: Thu, 01 Sep 2022 02:40:15 +0000 [thread overview]
Message-ID: <166200001508.20120.648796075645214084.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220825080420.1282569-1-jiri@resnulli.us>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel•org>:
On Thu, 25 Aug 2022 10:04:18 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia•com>
>
> This patchset contains couple of small patches that allow user to run
> devlink commands in parallel, if kernel is capable of doing so.
>
> Jiri Pirko (2):
> devlink: load port-ifname map on demand
> devlink: fix parallel flash notifications processing
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] devlink: load port-ifname map on demand
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=5cddbb274eab
- [iproute2-next,2/2] devlink: fix parallel flash notifications processing
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=2b392dac5be3
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:[~2022-09-01 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 8:04 [patch iproute2-next 0/2] devlink: allow parallel commands Jiri Pirko
2022-08-25 8:04 ` [patch iproute2-next 1/2] devlink: load port-ifname map on demand Jiri Pirko
2022-08-25 8:04 ` [patch iproute2-next 2/2] devlink: fix parallel flash notifications processing Jiri Pirko
2022-09-01 2:40 ` 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=166200001508.20120.648796075645214084.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=dsahern@gmail$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=moshe@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeedm@nvidia$(echo .)com \
--cc=sthemmin@microsoft$(echo .)com \
--cc=vikas.gupta@broadcom$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox