From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: patchwork-bot+netdevbpf@kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, 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 12:37:09 -0800 [thread overview]
Message-ID: <20230130123709.2c52f600@kernel.org> (raw)
In-Reply-To: <Y9eg4OmDARyDHUFc@nanopsycho>
On Mon, 30 Jan 2023 11:50:08 +0100 Jiri Pirko wrote:
> 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?
Hah :D
It's done locally, not by the bot. Our (Daniel Borkmann's) script
fetches the author from patchwork, but I think DaveM has his own
automation.
prev parent reply other threads:[~2023-01-30 20:37 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
2023-01-30 20:37 ` Jakub Kicinski [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=20230130123709.2c52f600@kernel.org \
--to=kuba@kernel.org \
--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=jiri@resnulli.us \
--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).