From: Jiri Pirko <jiri@resnulli.us>
To: patchwork-bot+netdevbpf@kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
michael.chan@broadcom.com, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, tariqt@nvidia.com, saeedm@nvidia.com,
leon@kernel.org, idosch@nvidia.com, petrm@nvidia.com,
jacob.e.keller@intel.com, gal@nvidia.com,
mailhol.vincent@wanadoo.fr
Subject: Re: [patch net-next 0/3] devlink: fix reload notifications and remove features
Date: Mon, 30 Jan 2023 11:50:08 +0100 [thread overview]
Message-ID: <Y9eg4OmDARyDHUFc@nanopsycho> (raw)
In-Reply-To: <167506861691.21040.7506893085716379938.git-patchwork-notify@kernel.org>
Mon, Jan 30, 2023 at 09:50:16AM CET, patchwork-bot+netdevbpf@kernel.org wrote:
>Hello:
>
>This series was applied to netdev/net-next.git (master)
>by David S. Miller <davem@davemloft.net>:
>
>On Fri, 27 Jan 2023 16:50:39 +0100 you wrote:
>> From: Jiri Pirko <jiri@nvidia.com>
>>
>> First two patches adjust notifications during devlink reload.
>> The last patch removes no longer needed devlink features.
>>
>> Jiri Pirko (3):
>> devlink: move devlink reload notifications back in between _down() and
>> _up() calls
>> devlink: send objects notifications during devlink reload
>> devlink: remove devlink features
>>
>> [...]
>
>Here is the summary with links:
> - [net-next,1/3] devlink: move devlink reload notifications back in between _down() and _up() calls
> https://git.kernel.org/netdev/net-next/c/7d7e9169a3ec
> - [net-next,2/3] devlink: send objects notifications during devlink reload
> https://git.kernel.org/netdev/net-next/c/a131315a47bb
> - [net-next,3/3] devlink: remove devlink features
> https://git.kernel.org/netdev/net-next/c/fb8421a94c56
Hi.
The merge commit text is wrong:
Merge branch 'devlink-next'
Jakub Kicinski says:
====================
devlink: fix reload notifications and remove features
First two patches adjust notifications during devlink reload.
The last patch removes no longer needed devlink features.
"Jakub Kicinsky says" should be "Jiri Pirko says". I thought this is
done by a bot? Is the bot buggy?
>
>You are awesome, thank you!
>--
>Deet-doot-dot, I am a bot.
>https://korg.docs.kernel.org/patchwork/pwbot.html
>
>
next prev parent reply other threads:[~2023-01-30 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 15:50 [patch net-next 0/3] devlink: fix reload notifications and remove features Jiri Pirko
2023-01-27 15:50 ` [patch net-next 1/3] devlink: move devlink reload notifications back in between _down() and _up() calls Jiri Pirko
2023-01-28 0:08 ` Jacob Keller
2023-01-27 15:50 ` [patch net-next 2/3] devlink: send objects notifications during devlink reload Jiri Pirko
2023-01-28 0:08 ` Jacob Keller
2023-01-27 15:50 ` [patch net-next 3/3] devlink: remove devlink features Jiri Pirko
2023-01-28 0:08 ` Jacob Keller
2023-01-28 5:58 ` [patch net-next 0/3] devlink: fix reload notifications and remove features Jakub Kicinski
2023-01-30 8:50 ` patchwork-bot+netdevbpf
2023-01-30 10:50 ` Jiri Pirko [this message]
2023-01-30 20:37 ` Jakub Kicinski
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=Y9eg4OmDARyDHUFc@nanopsycho \
--to=jiri@resnulli.us \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=tariqt@nvidia.com \
--cc=yisen.zhuang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).