From: Adit Ranadive <aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Adit Ranadive <aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
pv-drivers-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org
Subject: [PATCH for-next v1 0/2] RDMA/vmw_pvrdma: Patches for 4.14
Date: Tue, 29 Aug 2017 15:51:28 -0700 [thread overview]
Message-ID: <cover.1504045411.git.aditr@vmware.com> (raw)
Hi Doug,
Here are a couple more patches for the VMware PVRDMA driver for 4.14.
These are based on your for-next branch.
Thanks,
Adit
---
Changes v0 -> v1:
- Dropped the PVRDMA network type enums and the conversion function.
---
Adit Ranadive (1):
RDMA/vmw_pvrdma: Fix a signedness
Aditya Sarwade (1):
RDMA/vmw_pvrdma: Report network header type in WC
drivers/infiniband/hw/vmw_pvrdma/pvrdma_cq.c | 3 ++-
include/uapi/rdma/vmw_pvrdma-abi.h | 6 ++++--
2 files changed, 6 insertions(+), 3 deletions(-)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-08-29 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 22:51 Adit Ranadive [this message]
[not found] ` <cover.1504045411.git.aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2017-08-29 22:51 ` [PATCH for-next v1 1/2] RDMA/vmw_pvrdma: Report network header type in WC Adit Ranadive
[not found] ` <2abd8333de3bb9a2e609f107b1826470a54d1c30.1504045411.git.aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2017-08-30 14:19 ` Yuval Shaia
2017-08-29 22:51 ` [PATCH for-next v1 2/2] RDMA/vmw_pvrdma: Fix a signedness Adit Ranadive
[not found] ` <41188f37ed9e524e6f53759ec92f9dd94c8b47a1.1504045412.git.aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2017-08-30 14:19 ` Yuval Shaia
2017-08-30 14:24 ` [PATCH for-next v1 0/2] RDMA/vmw_pvrdma: Patches for 4.14 Doug Ledford
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=cover.1504045411.git.aditr@vmware.com \
--to=aditr-pghwnbhtmq7qt0dzr+alfa@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pv-drivers-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org \
/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