All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>, Aya Levin <ayal@nvidia.com>,
	Jiri Pirko <jiri@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH net-next 0/2] Delete publish of single parameter API
Date: Tue, 14 Sep 2021 15:58:27 +0300	[thread overview]
Message-ID: <cover.1631623748.git.leonro@nvidia.com> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

Hi,

This short series removes the single parameter publish/unpublish API
that does nothing expect mimics already existing
devlink_paramss_*publish calls.

In near future, we will be able to delete devlink_paramss_*publish too.

Thanks

Leon Romanovsky (2):
  net/mlx5: Publish and unpublish all devlink parameters at once
  devlink: Delete not-used single parameter notification APIs

 .../net/ethernet/mellanox/mlx5/core/devlink.c | 10 +---
 include/net/devlink.h                         |  4 --
 net/core/devlink.c                            | 48 -------------------
 3 files changed, 2 insertions(+), 60 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-09-14 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 12:58 Leon Romanovsky [this message]
2021-09-14 12:58 ` [PATCH net-next 1/2] net/mlx5: Publish and unpublish all devlink parameters at once Leon Romanovsky
2021-09-14 12:58 ` [PATCH net-next 2/2] devlink: Delete not-used single parameter notification APIs Leon Romanovsky
2021-09-15  3:01   ` Jakub Kicinski
2021-09-15 15:20 ` [PATCH net-next 0/2] Delete publish of single parameter API 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.1631623748.git.leonro@nvidia.com \
    --to=leon@kernel.org \
    --cc=ayal@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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 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.