All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adit Ranadive <aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	pv-drivers-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org
Cc: Adit Ranadive <aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/2] Fixes for vmw_pvrdma
Date: Thu, 19 Jan 2017 13:20:38 -0800	[thread overview]
Message-ID: <cover.1484859556.git.aditr@vmware.com> (raw)

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(-)

-- 
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

             reply	other threads:[~2017-01-19 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 21:20 Adit Ranadive [this message]
     [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   ` [PATCH 0/2] Fixes for vmw_pvrdma 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.1484859556.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 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.