From: Doug Ledford <dledford@redhat.com>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>,
Stuart Summers <john.s.summers@intel.com>,
linux-rdma@vger.kernel.org, Ira Weiny <ira.weiny@intel.com>,
Mitko Haralanov <mitko.haralanov@intel.com>,
Tadeusz Struk <tadeusz.struk@intel.com>,
stable@vger.kernel.org,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
Easwar Hariharan <easwar.hariharan@intel.com>,
Don Hiatt <don.hiatt@intel.com>,
Neel Desai <neel.desai@intel.com>,
Leon Romanovsky <leonro@mellanox.com>,
Sebastian Sanchez <sebastian.sanchez@intel.com>,
Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@intel.com>
Subject: Re: [PATCH 00/20] IB/hfi1,rdmavt,core: Patches for-next
Date: Fri, 28 Apr 2017 14:09:05 -0400 [thread overview]
Message-ID: <1493402945.3041.165.camel@redhat.com> (raw)
In-Reply-To: <8747fd5c-9d71-3503-186c-8a6b8ca51e75@intel.com>
On Fri, 2017-04-28 at 13:50 -0400, Dennis Dalessandro wrote:
> On 04/28/2017 01:45 PM, Doug Ledford wrote:
> >
> > On Sun, 2017-04-09 at 10:15 -0700, Dennis Dalessandro wrote:
> > >
> > > Doug,
> > >
> > > Here are some patches for the next release. It includes the core
> > > fix
> > > that did
> > > not apply from my last series. Other than that this is the usual
> > > bug
> > > fixes
> > > and some minor clean ups.
> > >
> > > Patches apply on top of your for-4.12 branch and can also be
> > > found in
> > > my
> > > GitHub repo at: https://github.com/ddalessa/kernel/tree/for-4.12
> > >
> >
> > Series, minus patch #2 because of community NAK, applied.
> >
>
> Looks like we are working at the same time. A v2 was literally sent
> 5
> minutes ago. The only changes were to drop that NAKed patch and fix
> up
> the soft-lockup patch so if you just want to grab:
>
> https://patchwork.kernel.org/patch/9705175/
>
> to replace the original:
>
> https://patchwork.kernel.org/patch/9671675/
>
> That would be good or I could send a separate patch with the fix-
> ups.
> Whichever is easiest.
>
> -Denny
I grabbed the updated patch 11, it's all good.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
prev parent reply other threads:[~2017-04-28 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 17:15 [PATCH 00/20] IB/hfi1,rdmavt,core: Patches for-next Dennis Dalessandro
2017-04-09 17:15 ` [PATCH 01/20] IB/core: If the MGID/MLID pair is not on the list return an error Dennis Dalessandro
2017-04-09 17:15 ` [PATCH 04/20] IB/core: For multicast functions, verify that LIDs are multicast LIDs Dennis Dalessandro
2017-04-15 15:01 ` Leon Romanovsky
2017-04-09 17:16 ` [PATCH 11/20] IB/hfi1: Prevent kernel QP post send hard lockups Dennis Dalessandro
2017-04-09 17:17 ` [PATCH 20/20] IB/hfi1: Use bool in process_ecn Dennis Dalessandro
2017-04-28 17:45 ` [PATCH 00/20] IB/hfi1,rdmavt,core: Patches for-next Doug Ledford
2017-04-28 17:50 ` Dennis Dalessandro
2017-04-28 18:09 ` Doug Ledford [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=1493402945.3041.165.camel@redhat.com \
--to=dledford@redhat.com \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=dennis.dalessandro@intel.com \
--cc=don.hiatt@intel.com \
--cc=easwar.hariharan@intel.com \
--cc=ira.weiny@intel.com \
--cc=john.s.summers@intel.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.j.ruhl@intel.com \
--cc=mike.marciniszyn@intel.com \
--cc=mitko.haralanov@intel.com \
--cc=neel.desai@intel.com \
--cc=sebastian.sanchez@intel.com \
--cc=stable@vger.kernel.org \
--cc=tadeusz.struk@intel.com \
/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).