From: Leon Romanovsky <leonro@nvidia.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Ido Schimmel <idosch@nvidia.com>, Ingo Molnar <mingo@redhat.com>,
"Jiri Pirko" <jiri@nvidia.com>, <linux-kernel@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <mlxsw@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>, <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Salil Mehta <salil.mehta@huawei.com>,
Shay Drory <shayd@nvidia.com>,
Steven Rostedt <rostedt@goodmis.org>,
Tariq Toukan <tariqt@nvidia.com>,
Yisen Zhuang <yisen.zhuang@huawei.com>
Subject: Re: [PATCH net-next v3 0/5] devlink reload simplification
Date: Sat, 9 Oct 2021 11:16:22 +0300 [thread overview]
Message-ID: <YWFP1imsLsAP4Zwq@unreal> (raw)
In-Reply-To: <cover.1633589385.git.leonro@nvidia.com>
On Thu, Oct 07, 2021 at 09:55:14AM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
<...>
> Leon Romanovsky (5):
> devlink: Reduce struct devlink exposure
> devlink: Annotate devlink API calls
> devlink: Allow set reload ops callbacks separately
> net/mlx5: Separate reload devlink ops for multiport device
> devlink: Delete reload enable/disable interface
Hi,
I see in patchworks that state of this series was marked as "Rejected".
https://patchwork.kernel.org/project/netdevbpf/list/?series=558901&state=*
Can I ask why? How can we proceed with the series?
Thanks
>
> .../hisilicon/hns3/hns3pf/hclge_devlink.c | 7 +-
> .../hisilicon/hns3/hns3vf/hclgevf_devlink.c | 7 +-
> drivers/net/ethernet/mellanox/mlx4/main.c | 10 +-
> .../net/ethernet/mellanox/mlx5/core/devlink.c | 13 +-
> .../net/ethernet/mellanox/mlx5/core/main.c | 3 -
> .../mellanox/mlx5/core/sf/dev/driver.c | 5 +-
> drivers/net/ethernet/mellanox/mlxfw/mlxfw.h | 2 +-
> drivers/net/ethernet/mellanox/mlxsw/core.c | 19 +-
> drivers/net/netdevsim/dev.c | 13 +-
> include/net/devlink.h | 79 ++------
> include/trace/events/devlink.h | 72 ++++----
> net/core/devlink.c | 170 ++++++++++++------
> 12 files changed, 216 insertions(+), 184 deletions(-)
>
> --
> 2.31.1
>
prev parent reply other threads:[~2021-10-09 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 6:55 [PATCH net-next v3 0/5] devlink reload simplification Leon Romanovsky
2021-10-07 6:55 ` [PATCH net-next v3 1/5] devlink: Reduce struct devlink exposure Leon Romanovsky
2021-10-07 19:58 ` Steven Rostedt
2021-10-08 0:44 ` Leon Romanovsky
2021-10-07 6:55 ` [PATCH net-next v3 2/5] devlink: Annotate devlink API calls Leon Romanovsky
2021-10-07 6:55 ` [PATCH net-next v3 3/5] devlink: Allow set reload ops callbacks separately Leon Romanovsky
2021-10-07 6:55 ` [PATCH net-next v3 4/5] net/mlx5: Separate reload devlink ops for multiport device Leon Romanovsky
2021-10-07 6:55 ` [PATCH net-next v3 5/5] devlink: Delete reload enable/disable interface Leon Romanovsky
2021-10-09 8:16 ` Leon Romanovsky [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=YWFP1imsLsAP4Zwq@unreal \
--to=leonro@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=shayd@nvidia.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 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.