Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: zhang.yanze@zte.com.cn
Cc: jgg@ziepe.ca, julianbraha@gmail.com,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	wei.quan@zte.com.cn, han.junyang@zte.com.cn, ran.ming@zte.com.cn,
	han.chengfei@zte.com.cn
Subject: Re: [PATCH rdma v2 0/2] Add ZTE DingHai Ethernet Protocol Driver for RDMA
Date: Sun, 5 Jul 2026 14:29:15 +0300	[thread overview]
Message-ID: <20260705112915.GB15188@unreal> (raw)
In-Reply-To: <20260626165050955lBuUhmj0yLn5xCsQ-tbx4@zte.com.cn>

On Fri, Jun 26, 2026 at 04:50:50PM +0800, zhang.yanze@zte.com.cn wrote:
> From: Yanze Zhang <zhang.yanze@zte.com.cn>
> 
> Hi maintainers and reviewers,
> 
> This is v2 of the ZTE DingHai (ZXDH) RDMA driver submission.
> Thank you Julian Braha for the review on v1.
> 
> Changes in v2:
> - Removed redundant 'depends on INFINIBAND' from Kconfig as it is already
>   wrapped by the parent if-block (Julian Braha).
> 
> The driver provides RoCEv2 support for ZTE DingHai network adapters and has
> been tested with perftest and rping utilities.
> 
> Best regards,
> Yanze Zhang
> 
> Yanze Zhang (2):
> RDMA/zrdma: Add ZTE Dinghai Ethernet Protocol Driver for RDMA
> RDMA/zrdma: Add hardware config code and improve driver init flow

1. Split this driver into smaller patches to simplify review.
2. Remove unused defines and functions from the driver.
3. The driver must be functional. It cannot operate without a
   driver ID.
4. Please refresh your
   https://github.com/linux-rdma/rdma-core/pull/1611 PR.

Thanks

      parent reply	other threads:[~2026-07-05 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  8:50 [PATCH rdma v2 0/2] Add ZTE DingHai Ethernet Protocol Driver for RDMA zhang.yanze
2026-06-26  8:53 ` [PATCH rdma v2 1/2] RDMA/zrdma: Add basic framework for ZTE Dinghai " zhang.yanze
2026-06-26  8:55 ` [PATCH rdma v2 2/2] RDMA/zrdma: Add hardware config code and improve driver init flow zhang.yanze
2026-07-05 11:29 ` 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=20260705112915.GB15188@unreal \
    --to=leon@kernel.org \
    --cc=han.chengfei@zte.com.cn \
    --cc=han.junyang@zte.com.cn \
    --cc=jgg@ziepe.ca \
    --cc=julianbraha@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=ran.ming@zte.com.cn \
    --cc=wei.quan@zte.com.cn \
    --cc=zhang.yanze@zte.com.cn \
    /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