Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Cheng Xu <chengyou@linux.alibaba.com>
To: jgg@ziepe.ca, dledford@redhat.com, leon@kernel.org
Cc: linux-rdma@vger.kernel.org, KaiShen@linux.alibaba.com,
	tonylu@linux.alibaba.com, BMT@zurich.ibm.com
Subject: Re: [PATCH for-next v5 00/12] Elastic RDMA Adapter (ERDMA) driver
Date: Mon, 11 Apr 2022 10:52:23 +0800	[thread overview]
Message-ID: <4bd2e278-bb7e-1b7b-ba01-84a1a0d01958@linux.alibaba.com> (raw)
In-Reply-To: <20220406023450.56683-1-chengyou@linux.alibaba.com>



On 4/6/22 10:34 AM, Cheng Xu wrote:
> Hello all,
> 

<...>

Hello, Jason and Leon,

This v5 patchset has a compilation issue with the latest for-next
branch, due to "pci_dma_compat.h" was removed in kernel 5.18. And it
will have another compilation issue with the "device_cap_flags" [1], but
I didn't see the changes in for-next branch for now.

I will fix them together and send another patchset after the changes in
[1] are present in for-next branch.

[1] 
https://lore.kernel.org/netdev/0-v2-22c19e565eef+139a-kern_caps_jgg@nvidia.com/

Thanks,
Cheng Xu

> Cheng Xu (12):
>    RDMA: Add ERDMA to rdma_driver_id definition
>    RDMA/core: Allow calling query_port when netdev isn't attached in
>      iWarp
>    RDMA/erdma: Add the hardware related definitions
>    RDMA/erdma: Add main include file
>    RDMA/erdma: Add cmdq implementation
>    RDMA/erdma: Add event queue implementation
>    RDMA/erdma: Add verbs header file
>    RDMA/erdma: Add verbs implementation
>    RDMA/erdma: Add connection management (CM) support
>    RDMA/erdma: Add the erdma module
>    RDMA/erdma: Add the ABI definitions
>    RDMA/erdma: Add driver to kernel build environment
> 
>   MAINTAINERS                               |    8 +
>   drivers/infiniband/Kconfig                |    1 +
>   drivers/infiniband/core/device.c          |    7 +-
>   drivers/infiniband/hw/Makefile            |    1 +
>   drivers/infiniband/hw/erdma/Kconfig       |   12 +
>   drivers/infiniband/hw/erdma/Makefile      |    4 +
>   drivers/infiniband/hw/erdma/erdma.h       |  288 ++++
>   drivers/infiniband/hw/erdma/erdma_cm.c    | 1434 ++++++++++++++++++++
>   drivers/infiniband/hw/erdma/erdma_cm.h    |  168 +++
>   drivers/infiniband/hw/erdma/erdma_cmdq.c  |  497 +++++++
>   drivers/infiniband/hw/erdma/erdma_cq.c    |  205 +++
>   drivers/infiniband/hw/erdma/erdma_eq.c    |  334 +++++
>   drivers/infiniband/hw/erdma/erdma_hw.h    |  504 +++++++
>   drivers/infiniband/hw/erdma/erdma_main.c  |  631 +++++++++
>   drivers/infiniband/hw/erdma/erdma_qp.c    |  564 ++++++++
>   drivers/infiniband/hw/erdma/erdma_verbs.c | 1454 +++++++++++++++++++++
>   drivers/infiniband/hw/erdma/erdma_verbs.h |  342 +++++
>   include/uapi/rdma/erdma-abi.h             |   49 +
>   include/uapi/rdma/ib_user_ioctl_verbs.h   |    1 +
>   19 files changed, 6503 insertions(+), 1 deletion(-)
>   create mode 100644 drivers/infiniband/hw/erdma/Kconfig
>   create mode 100644 drivers/infiniband/hw/erdma/Makefile
>   create mode 100644 drivers/infiniband/hw/erdma/erdma.h
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_cm.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_cm.h
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_cmdq.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_cq.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_eq.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_hw.h
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_main.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_qp.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_verbs.c
>   create mode 100644 drivers/infiniband/hw/erdma/erdma_verbs.h
>   create mode 100644 include/uapi/rdma/erdma-abi.h
> 

      parent reply	other threads:[~2022-04-11  2:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  2:34 [PATCH for-next v5 00/12] Elastic RDMA Adapter (ERDMA) driver Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 01/12] RDMA: Add ERDMA to rdma_driver_id definition Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 02/12] RDMA/core: Allow calling query_port when netdev isn't attached in iWarp Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 03/12] RDMA/erdma: Add the hardware related definitions Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 04/12] RDMA/erdma: Add main include file Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 05/12] RDMA/erdma: Add cmdq implementation Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 06/12] RDMA/erdma: Add event queue implementation Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 07/12] RDMA/erdma: Add verbs header file Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 08/12] RDMA/erdma: Add verbs implementation Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 09/12] RDMA/erdma: Add connection management (CM) support Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 10/12] RDMA/erdma: Add the erdma module Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 11/12] RDMA/erdma: Add the ABI definitions Cheng Xu
2022-04-06  2:34 ` [PATCH for-next v5 12/12] RDMA/erdma: Add driver to kernel build environment Cheng Xu
2022-04-11  2:52 ` Cheng Xu [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=4bd2e278-bb7e-1b7b-ba01-84a1a0d01958@linux.alibaba.com \
    --to=chengyou@linux.alibaba.com \
    --cc=BMT@zurich.ibm.com \
    --cc=KaiShen@linux.alibaba.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tonylu@linux.alibaba.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