From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: <zyjzyj2000@gmail.com>, <linux-rdma@vger.kernel.org>,
Bob Pearson <rpearson@hpe.com>
Subject: Re: [PATCH for-next] provider/rxe: Support UD network_type patch
Date: Fri, 16 Oct 2020 19:25:14 -0300 [thread overview]
Message-ID: <20201016222514.GU6219@nvidia.com> (raw)
In-Reply-To: <20201016212459.23140-1-rpearson@hpe.com>
On Fri, Oct 16, 2020 at 04:25:00PM -0500, Bob Pearson wrote:
> The patch referenced below changed the type of the enum to be returned in
> send WQEs to the kernel. This patch makes the corresponding change to the
> rxe provider. Without this change the driver is not functional.
?? The enum values didn't change so it should be functional, right?
> Reference: e0d696d201dd ("RDMA/rxe: Move the definitions for rxe_av.network_type to uAPI")
> Signed-off-by: Bob Pearson <rpearson@hpe.com>
> kernel-headers/rdma/rdma_user_rxe.h | 6 ++++++
> providers/rxe/rxe.c | 2 +-
> providers/rxe/rxe.h | 6 ------
> 3 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/kernel-headers/rdma/rdma_user_rxe.h b/kernel-headers/rdma/rdma_user_rxe.h
> index d8f2e0e4..e591d8c1 100644
> +++ b/kernel-headers/rdma/rdma_user_rxe.h
> @@ -39,6 +39,11 @@
> #include <linux/in.h>
> #include <linux/in6.h>
Updating kernel-headers/ requires two commits the first is made
automatically by the kernel-headers/update script which keeps
everything in sync
Jason
prev parent reply other threads:[~2020-10-16 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 21:25 [PATCH for-next] provider/rxe: Support UD network_type patch Bob Pearson
2020-10-16 21:44 ` Pearson, Robert B
2020-10-16 22:25 ` 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=20201016222514.GU6219@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.com \
--cc=rpearsonhpe@gmail.com \
--cc=zyjzyj2000@gmail.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;
as well as URLs for NNTP newsgroup(s).