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, Kaike Wan <kaike.wan@intel.com>
Subject: Re: [PATCH for-rc 0/2] IB/hfi1: Fixes for rc or next if too late
Date: Mon, 4 Jun 2018 13:34:48 -0600 [thread overview]
Message-ID: <20180604193448.GA27896@ziepe.ca> (raw)
In-Reply-To: <20180531182633.26542.10152.stgit@scvm10.sc.intel.com>
On Thu, May 31, 2018 at 11:29:59AM -0700, Dennis Dalessandro wrote:
> Hi Doug and Jason,
>
> We have two more late breaking fix up patches. The DMA_RTAIL fix is the more
> serious of the two. I realize we are at the tail end of 4.17 so I would not be
> against holding off till 4.18 for these, but if there is another rdma
> pull request we may want to tack these on.
>
>
> Kaike Wan (1):
> IB/hfi1: Ensure VL index is within bounds
>
> Mike Marciniszyn (1):
> IB/hfi1: Fix user context tail allocation for DMA_RTAIL
applied to for-next since the merge window is open now
Thanks,
Jason
prev parent reply other threads:[~2018-06-04 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 18:29 [PATCH for-rc 0/2] IB/hfi1: Fixes for rc or next if too late Dennis Dalessandro
2018-05-31 18:30 ` [PATCH for-rc 1/2] IB/hfi1: Fix user context tail allocation for DMA_RTAIL Dennis Dalessandro
2018-05-31 18:47 ` [PATCH for-rc 0/2] IB/hfi1: Fixes for rc or next if too late Doug Ledford
2018-05-31 19:08 ` Dennis Dalessandro
2018-05-31 20:21 ` Jason Gunthorpe
2018-05-31 20:29 ` Dennis Dalessandro
2018-06-04 19:34 ` 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=20180604193448.GA27896@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=kaike.wan@intel.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;
as well as URLs for NNTP newsgroup(s).