From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
linux-rdma@vger.kernel.org, stable@vger.kernel.org,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
Lukasz Odzioba <lukasz.odzioba@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH for-rc 0/4] IB/hfi1: Couple more for the RC cycle
Date: Thu, 20 Sep 2018 19:26:26 -0600 [thread overview]
Message-ID: <20180921012626.GA13768@ziepe.ca> (raw)
In-Reply-To: <20180920195649.20625.38869.stgit@scvm10.sc.intel.com>
On Thu, Sep 20, 2018 at 12:58:34PM -0700, Dennis Dalessandro wrote:
> Hi Doug and Jason,
>
> Mike and Ira have identified some fixes that they would like to see land in the
> RC, these are serious problems and are marked as stable.
>
> Changes since v1:
> Update Lukasz' email address and fix subject tag.
>
> ---
>
> Ira Weiny (1):
> IB/hfi1: Fix SL array bounds check
>
> Michael J. Ruhl (3):
> IB/hfi1: Invalid user input can result in crash
> IB/hfi1: Fix context recovery when PBC has an UnsupportedVL
> IB/hfi1: Fix destroy_qp hang after a link down
Applied to for-rc, thanks
Jason
prev parent reply other threads:[~2018-09-21 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 19:58 [PATCH for-rc 0/4] IB/hfi1: Couple more for the RC cycle Dennis Dalessandro
2018-09-20 19:58 ` [PATCH for-rc 1/4] IB/hfi1: Fix SL array bounds check Dennis Dalessandro
2018-09-20 19:58 ` [PATCH for-rc 2/4] IB/hfi1: Invalid user input can result in crash Dennis Dalessandro
2018-09-20 19:59 ` [PATCH for-rc 3/4] IB/hfi1: Fix context recovery when PBC has an UnsupportedVL Dennis Dalessandro
2018-09-20 19:59 ` [PATCH for-rc 4/4] IB/hfi1: Fix destroy_qp hang after a link down Dennis Dalessandro
2018-09-21 1:26 ` 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=20180921012626.GA13768@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=ira.weiny@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lukasz.odzioba@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).