From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH for-next 0/3] Driver fixes
Date: Mon, 4 Mar 2019 15:49:35 -0400 [thread overview]
Message-ID: <20190304194935.GB1816@ziepe.ca> (raw)
In-Reply-To: <20190226164333.31476.43732.stgit@scvm10.sc.intel.com>
On Tue, Feb 26, 2019 at 08:45:02AM -0800, Dennis Dalessandro wrote:
> Hi Jason and Doug,
>
> Here are some fixes that didn't quite make the boat for 5.0-rc. So we can
> go ahead and send them to -next. The third patch here is really a v2 of:
>
> https://patchwork.kernel.org/patch/10769005/
>
>
> Michael J. Ruhl (2):
> IB/rdmavt: Fix concurrency panics in QP post_send and modify to error
> IB/hfi1: Close race condition on user context disable and close
>
> Mike Marciniszyn (1):
> IB/rdmavt: Fix loopback send with invalidate ordering
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2019-03-04 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:45 [PATCH for-next 0/3] Driver fixes Dennis Dalessandro
2019-02-26 16:45 ` [PATCH for-next 1/3] IB/rdmavt: Fix loopback send with invalidate ordering Dennis Dalessandro
2019-02-26 16:45 ` [PATCH for-next 2/3] IB/rdmavt: Fix concurrency panics in QP post_send and modify to error Dennis Dalessandro
2019-02-26 16:45 ` [PATCH for-next 3/3] IB/hfi1: Close race condition on user context disable and close Dennis Dalessandro
2019-02-26 17:15 ` Dennis Dalessandro
2019-03-04 20:41 ` Jason Gunthorpe
2019-03-05 15:30 ` Dennis Dalessandro
2019-03-06 18:47 ` Jason Gunthorpe
2019-03-04 19:49 ` 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=20190304194935.GB1816@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.j.ruhl@intel.com \
--cc=mike.marciniszyn@intel.com \
--cc=stable@vger.kernel.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