From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Adit Ranadive <aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
pv-drivers-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 0/2] Fixes for vmw_pvrdma
Date: Tue, 24 Jan 2017 14:16:51 -0500 [thread overview]
Message-ID: <1485285411.43764.40.camel@redhat.com> (raw)
In-Reply-To: <cover.1484859556.git.aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
On Thu, 2017-01-19 at 13:20 -0800, Adit Ranadive wrote:
> Hi Doug,
>
> Here are the fixes for vmw_pvrdma for this round of rc. These apply
> cleanly to your k.o/for-4.10-rc branch.
>
> Thanks,
> Adit
>
> Adit Ranadive (2):
> IB/vmw_pvrdma: Don't leak info from alloc_ucontext
> IB/vmw_pvrdma: Fix incorrect cleanup on pvrdma_pci_probe error path
>
> drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c | 4 +---
> drivers/infiniband/hw/vmw_pvrdma/pvrdma_verbs.c | 2 +-
> 2 files changed, 2 insertions(+), 4 deletions(-)
Thanks, series applied.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-01-24 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 21:20 [PATCH 0/2] Fixes for vmw_pvrdma Adit Ranadive
[not found] ` <cover.1484859556.git.aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2017-01-19 21:20 ` [PATCH 1/2] IB/vmw_pvrdma: Don't leak info from alloc_ucontext Adit Ranadive
2017-01-19 21:20 ` [PATCH 2/2] IB/vmw_pvrdma: Fix incorrect cleanup on pvrdma_pci_probe error path Adit Ranadive
[not found] ` <cd1027c125c3c098c59fa3c612e6bf617aa77dc9.1484859556.git.aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2017-01-23 8:45 ` Yuval Shaia
2017-01-24 19:16 ` Doug Ledford [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=1485285411.43764.40.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=aditr-pghWNbHTmq7QT0dZR+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;
as well as URLs for NNTP newsgroup(s).