From: Jakub Kicinski <kuba@kernel•org>
To: Jiri Pirko <jiri@resnulli•us>
Cc: 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: Fri, 27 Jan 2023 21:58:15 -0800 [thread overview]
Message-ID: <20230127215815.1304c2a9@kernel.org> (raw)
In-Reply-To: <20230127155042.1846608-1-jiri@resnulli.us>
On Fri, 27 Jan 2023 16:50:39 +0100 Jiri Pirko wrote:
> From: Jiri Pirko <jiri@nvidia•com>
>
> First two patches adjust notifications during devlink reload.
> The last patch removes no longer needed devlink features.
Reviewed-by: Jakub Kicinski <kuba@kernel•org>
Thanks!
next prev parent reply other threads:[~2023-01-28 5:58 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 ` Jakub Kicinski [this message]
2023-01-30 8:50 ` [patch net-next 0/3] devlink: fix reload notifications and remove features patchwork-bot+netdevbpf
2023-01-30 10:50 ` Jiri Pirko
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=20230127215815.1304c2a9@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=leon@kernel$(echo .)org \
--cc=mailhol.vincent@wanadoo$(echo .)fr \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=salil.mehta@huawei$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
--cc=yisen.zhuang@huawei$(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