linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com,
	Mike Mariciniszyn <mike.marciniszyn@intel.com>,
	linux-rdma@vger.kernel.org,
	Mitko Haralanov <mitko.haralanov@intel.com>,
	Brian Welty <brian.welty@intel.com>,
	Alex Estrin <alex.estrin@intel.com>,
	stable@vger.kernel.org, Ashutosh Dixit <ashutosh.dixit@intel.com>,
	"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
	Harish Chegondi <harish.chegondi@intel.com>,
	Don Hiatt <don.hiatt@intel.com>,
	Sebastian Sanchez <sebastian.sanchez@intel.com>,
	Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
Subject: Re: [PATCH for-next 00/13] IB/hfi1,core: Driver updates for 4.17
Date: Tue, 17 Apr 2018 19:40:53 -0600	[thread overview]
Message-ID: <20180418014053.GA10098@ziepe.ca> (raw)
In-Reply-To: <20180405025915.18766.41569.stgit@scvm10.sc.intel.com>

On Wed, Apr 04, 2018 at 08:01:11PM -0700, Dennis Dalessandro wrote:
> Hi Jason and Doug,
> 
> Here are most of our updates for 4.17. I will follow this up with a small
> 16B series then I still have a few more patches that are waiting on
> some more thorough testing. Should be able to get them on the list tomrrow or
> Friday at the latest, wanted to get these out now. I don't think anything
> is really that scary in here.
> 
> These are mostly driver fixes. Patches 4,7,8,11, and 14 are marked stable.
> They didn't get sent for the -rc because they fix really old issues.
> 
> Patch 5 is a core fix. I should have sent it a bit sooner, sorry about that but
> it's pretty trivial so I decided to include it as well rather than wait for
> 4.18.
> 
> 
> Alex Estrin (2):
>       IB/hfi1: Complete check for locally terminated smp
>       IB/{hfi1,qib}: Add handling of kernel restart
> 
> Ashutosh Dixit (1):
>       IB/core: Fix rkey invalidation from user space into the kernel
> 
> Michael J. Ruhl (5):
>       IB/hfi1: Return actual error value from program_rcvarray()
>       IB/hfi1: Use after free race condition in send context error path
>       IB/hfi1 Use correct type for num_user_context
>       IB/hfi1: Return correct value for device state
>       IB/hfi1: Reorder incorrect send context disable
> 
> Mike Marciniszyn (3):
>       IB/hfi1: Fix handling of FECN marked multicast packet
>       IB/hfi1: Fix fault injection init/exit issues
>       IB/hfi1: Fix loss of BECN with AHG
> 
> Sebastian Sanchez (2):
>       IB/hfi1: Prevent LNI hang when LCB can't obtain lanes
>       IB/{hfi1,rdmavt,qib}: Fit kernel completions into single aligned cache-line

Many of these got comments so I'm just going to drop the
series. Please rebase and resend anything you think should go to -rc
or -next that doesn't interact with the patches being revised.

Also let me know if the next '16B' series is independent of this, if
yes I'll drop it to..

Jason

  parent reply	other threads:[~2018-04-18  1:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  3:01 [PATCH for-next 00/13] IB/hfi1,core: Driver updates for 4.17 Dennis Dalessandro
2018-04-05  3:01 ` [PATCH for-next 04/13] IB/hfi1: Fix handling of FECN marked multicast packet Dennis Dalessandro
2018-04-05  3:02 ` [PATCH for-next 07/13] IB/hfi1: Fix fault injection init/exit issues Dennis Dalessandro
2018-04-05  3:02 ` [PATCH for-next 08/13] IB/hfi1: Use after free race condition in send context error path Dennis Dalessandro
2018-04-05  3:03 ` [PATCH for-next 11/13] IB/hfi1: Reorder incorrect send context disable Dennis Dalessandro
2018-04-05  3:03 ` [PATCH for-next 12/13] IB/{hfi1, qib}: Add handling of kernel restart Dennis Dalessandro
2018-04-05 19:17   ` Jason Gunthorpe
2018-04-11 18:43     ` Estrin, Alex
2018-04-05  3:03 ` [PATCH for-next 13/13] IB/hfi1: Fix loss of BECN with AHG Dennis Dalessandro
2018-04-05  3:09 ` [PATCH for-next 00/13] IB/hfi1,core: Driver updates for 4.17 Jason Gunthorpe
2018-04-05  3:33   ` Dennis Dalessandro
2018-04-05  4:09     ` Bart Van Assche
2018-04-05 14:49     ` Jason Gunthorpe
2018-04-18  1:40 ` Jason Gunthorpe [this message]
2018-04-18  2:56   ` Dennis Dalessandro

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=20180418014053.GA10098@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=alex.estrin@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=brian.welty@intel.com \
    --cc=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=don.hiatt@intel.com \
    --cc=harish.chegondi@intel.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michael.j.ruhl@intel.com \
    --cc=mike.marciniszyn@intel.com \
    --cc=mitko.haralanov@intel.com \
    --cc=prathap.kumar.valsan@intel.com \
    --cc=sebastian.sanchez@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).