From: Leon Romanovsky <leon@kernel.org>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next 0/4] Delete impossible devlink notifications
Date: Thu, 21 Oct 2021 17:16:12 +0300 [thread overview]
Message-ID: <cover.1634825474.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
This series is a followup to the delayed devlink notification scheme.
I removed the impossible notifications together with attempt to annotate
various calls in order to mark them as pre/post devlink)register().
Other notifications are called before and after delvink_register() so
they weren't changed in this pathcset.
Thanks
Leon Romanovsky (4):
devlink: Delete obsolete parameters publish API
devlink: Remove not-executed trap policer notifications
devlink: Remove not-executed trap group notifications
devlink: Clean not-executed param notifications
include/net/devlink.h | 3 --
net/core/devlink.c | 96 +++++++++++++------------------------------
2 files changed, 29 insertions(+), 70 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-21 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 14:16 Leon Romanovsky [this message]
2021-10-21 14:16 ` [PATCH net-next 1/4] devlink: Delete obsolete parameters publish API Leon Romanovsky
2021-10-21 14:16 ` [PATCH net-next 2/4] devlink: Remove not-executed trap policer notifications Leon Romanovsky
2021-10-21 14:16 ` [PATCH net-next 3/4] devlink: Remove not-executed trap group notifications Leon Romanovsky
2021-10-21 14:16 ` [PATCH net-next 4/4] devlink: Clean not-executed param notifications Leon Romanovsky
2021-10-22 23:30 ` [PATCH net-next 0/4] Delete impossible devlink notifications patchwork-bot+netdevbpf
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=cover.1634825474.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.