From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-rc 0/4] Few more rc fixes
Date: Wed, 6 Nov 2019 13:26:53 -0400 [thread overview]
Message-ID: <20191106172653.GA12905@ziepe.ca> (raw)
In-Reply-To: <20191025161717.106825.14421.stgit@awfm-01.aw.intel.com>
On Fri, Oct 25, 2019 at 03:58:17PM -0400, Dennis Dalessandro wrote:
> Here we have 4 more bug fixing patches. These are all marked stable as well so
> it would be good to get these in to 5.4 if possible.
>
> The allow for speeds patch is not a "feature" it is a bug that causes problems
> if the host comes up in gen4. Is very small. The other 3 from Kaike fix TID RDMA
> bugs. A few more lines of code here but all relegated to TID RDMA.
>
>
> James Erwin (1):
> IB/hfi1: Allow for all speeds higher than gen3
With v2 of this one
> Kaike Wan (3):
> IB/hfi1: Ensure r_tid_ack is valid before building TID RDMA ACK packet
> IB/hfi1: Calculate flow weight based on QP MTU for TID RDMA
> IB/hfi1: TID RDMA WRITE should not return IB_WC_RNR_RETRY_EXC_ERR
Applied to for-rc, thanks
Jason
prev parent reply other threads:[~2019-11-06 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 19:58 [PATCH for-rc 0/4] Few more rc fixes Dennis Dalessandro
2019-10-25 19:58 ` [PATCH for-rc 1/4] IB/hfi1: Allow for all speeds higher than gen3 Dennis Dalessandro
2019-10-29 19:52 ` Jason Gunthorpe
2019-10-29 21:19 ` Marciniszyn, Mike
2019-10-30 18:07 ` Jason Gunthorpe
2019-10-30 20:14 ` Marciniszyn, Mike
2019-11-01 19:39 ` Marciniszyn, Mike
2019-10-25 19:58 ` [PATCH for-rc 2/4] IB/hfi1: Ensure r_tid_ack is valid before building TID RDMA ACK packet Dennis Dalessandro
2019-10-25 19:58 ` [PATCH for-rc 3/4] IB/hfi1: Calculate flow weight based on QP MTU for TID RDMA Dennis Dalessandro
2019-10-25 19:58 ` [PATCH for-rc 4/4] IB/hfi1: TID RDMA WRITE should not return IB_WC_RNR_RETRY_EXC_ERR Dennis Dalessandro
2019-11-06 17: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=20191106172653.GA12905@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@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).