All of lore.kernel.org
 help / color / mirror / Atom feed
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, Alex Estrin <alex.estrin@intel.com>,
	stable@vger.kernel.org, Kaike Wan <kaike.wan@intel.com>,
	"Michael J. Ruhl" <michael.j.ruhl@intel.com>
Subject: Re: [PATCH for-rc 0/5] IB/hfi1: Fixes for 5.1 rc cycle
Date: Wed, 27 Mar 2019 14:58:06 -0300	[thread overview]
Message-ID: <20190327175806.GA32589@ziepe.ca> (raw)
In-Reply-To: <20190318165205.23550.97894.stgit@scvm10.sc.intel.com>

On Mon, Mar 18, 2019 at 09:54:55AM -0700, Dennis Dalessandro wrote:
> Here is a set of small fixes that we would like to land in the rc cycle
> for 5.1. One of them is marked as stable.
> 
> The first patch fixes an unnecessary stack trace due to incorrect WQ flags. The
> next three fix issues uncovered due to TID RDMA which was brought in for 5.1.
> The last one is a bug in VNIC.
> 
> 
> Kaike Wan (4):
>       IB/hfi1: Failed to drain send queue when QP is put into error state
>       IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state
>       IB/hfi1: Eliminate opcode tests on mr deref
>       IB/hfi1: Fix the allocation of RSM table

Applied these ones to for-rc

> Mike Marciniszyn (1):
>       IB/hfi1: Fix WQ_MEM_RECLAIM warning

Let us see how the discussion goes here

Thanks,
Jason

      parent reply	other threads:[~2019-03-27 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 16:54 [PATCH for-rc 0/5] IB/hfi1: Fixes for 5.1 rc cycle Dennis Dalessandro
2019-03-18 16:54 ` Dennis Dalessandro
2019-03-18 16:55 ` [PATCH for-rc 2/5] IB/hfi1: Failed to drain send queue when QP is put into error state Dennis Dalessandro
     [not found]   ` <20190325003824.8A64D20989@mail.kernel.org>
2019-03-25 12:32     ` Jason Gunthorpe
2019-03-27 17:58 ` 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=20190327175806.GA32589@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=alex.estrin@intel.com \
    --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 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.