public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Mark Zhang <markzhang@nvidia.com>
Cc: dsahern@gmail.com, jgg@nvidia.com, linux-rdma@vger.kernel.org
Subject: Re: [RFC iproute2-next 0/2] Supports to add/delete IB devices with type SMI
Date: Thu, 4 Jul 2024 08:01:27 +0300	[thread overview]
Message-ID: <20240704050127.GC95824@unreal> (raw)
In-Reply-To: <20240701083112.1793515-1-markzhang@nvidia.com>

On Mon, Jul 01, 2024 at 11:31:10AM +0300, Mark Zhang wrote:
> This series supports to add/delete an IB device with type SMI. This is
> complimentary to the kernel patches that support to IB sub device
> and mlx5 implementation.
> 
> https://lore.kernel.org/all/cover.1718553901.git.leon@kernel.org/
> 
> There's no kernel commit ID for the rdma_netlink.h change as the kernel
> part isn't accepted yet.
> 
> Thanks
> 
> Mark Zhang (2):
>   Update rdma_netlink.h file upto kernel commit

Kernel part was accepted, please resend this series with the updated
first commit.

Thanks

>   rdma: Supports to add/delete a device with type SMI
> 
>  man/man8/rdma-dev.8                   |  40 +++++++++
>  rdma/dev.c                            | 120 ++++++++++++++++++++++++++
>  rdma/include/uapi/rdma/rdma_netlink.h |  13 +++
>  rdma/rdma.h                           |   2 +
>  rdma/utils.c                          |   2 +
>  5 files changed, 177 insertions(+)
> 
> -- 
> 2.26.3
> 
> 

      parent reply	other threads:[~2024-07-04  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  8:31 [RFC iproute2-next 0/2] Supports to add/delete IB devices with type SMI Mark Zhang
2024-07-01  8:31 ` [RFC iproute2-next 1/2] Update rdma_netlink.h file upto kernel commit Mark Zhang
2024-07-01  8:31 ` [RFC iproute2-next 2/2] rdma: Supports to add/delete a device with type SMI Mark Zhang
2024-07-04  5:01 ` 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=20240704050127.GC95824@unreal \
    --to=leon@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markzhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox