From: Jason Gunthorpe <jgg@nvidia.com>
To: Chuck Lever <cel@kernel.org>
Cc: leon@kernel.org, Chuck Lever <chuck.lever@oracle.com>,
Tom Talpey <tom@talpey.com>, Bernard Metzler <bmt@zurich.ibm.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Handle ARPHRD_NONE devices for siw
Date: Fri, 21 Jul 2023 16:08:50 -0300 [thread overview]
Message-ID: <ZLrXwqE7xXiEF37D@nvidia.com> (raw)
In-Reply-To: <168960662017.3007.17697555924773191374.stgit@manet.1015granger.net>
On Mon, Jul 17, 2023 at 11:12:05AM -0400, Chuck Lever wrote:
> Here's a series that implements support for siw on tunnel devices,
> based on suggestions from Jason Gunthorpe and Tom Talpey.
>
>
> Changes since v5:
> - Refine comment in cma_validate_port()
>
> Changes since v4:
> - Address review comments from Tom Talpey
>
> Changes since v3:
> - Clean up RCU dereference in cma_validate_port()
>
> Changes since v2:
> - Split into multiple patches
> - Pre-initialize gid_attr::ndev for iWARP devices
>
> ---
>
> Chuck Lever (4):
> RDMA/siw: Fabricate a GID on tun and loopback devices
> RDMA/core: Set gid_attr.ndev for iWARP devices
> RDMA/cma: Deduplicate error flow in cma_validate_port()
> RDMA/cma: Avoid GID lookups on iWARP devices
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2023-07-21 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 15:12 [PATCH v6 0/4] Handle ARPHRD_NONE devices for siw Chuck Lever
2023-07-17 15:12 ` [PATCH v6 1/4] RDMA/siw: Fabricate a GID on tun and loopback devices Chuck Lever
2023-07-17 15:12 ` [PATCH v6 2/4] RDMA/core: Set gid_attr.ndev for iWARP devices Chuck Lever
2023-07-17 15:12 ` [PATCH v6 3/4] RDMA/cma: Deduplicate error flow in cma_validate_port() Chuck Lever
2023-07-17 15:12 ` [PATCH v6 4/4] RDMA/cma: Avoid GID lookups on iWARP devices Chuck Lever
2023-07-21 19:08 ` Jason Gunthorpe [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=ZLrXwqE7xXiEF37D@nvidia.com \
--to=jgg@nvidia.com \
--cc=bmt@zurich.ibm.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tom@talpey.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.