From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Dalessandro, Dennis" <dennis.dalessandro@intel.com>,
"dledford@redhat.com" <dledford@redhat.com>
Subject: Re: FAILED: patch "[PATCH] IB/hfi1: Fix deadlock with txreq allocation slow path" failed to apply to 4.6-stable tree
Date: Wed, 20 Jul 2016 14:49:12 -0700 [thread overview]
Message-ID: <20160720214912.GA14708@kroah.com> (raw)
In-Reply-To: <32E1700B9017364D9B60AED9960492BC2D05682C@fmsmsx120.amr.corp.intel.com>
On Wed, Jul 20, 2016 at 09:17:30PM +0000, Marciniszyn, Mike wrote:
> > The patch below does not apply to the 4.6-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > thanks,
> >
> > greg k-h
>
> A 4.6 version is in http://marc.info/?l=linux-rdma&m=146904918032092&w=2.
I can't do much with a web-link, can you send me the patch?
> Oddly it cherry-picked for me ok. Is this due to a flaw in the stable triggering method in the upstream patch?
Hm, if cherry-pick worked, that's a huge hint, can you send me the
cherry-picked patch output? Odds are git can handle a merge issue
better than quilt can.
thanks,
greg k-h
next prev parent reply other threads:[~2016-07-20 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 22:18 FAILED: patch "[PATCH] IB/hfi1: Fix deadlock with txreq allocation slow path" failed to apply to 4.6-stable tree gregkh
2016-07-20 21:17 ` Marciniszyn, Mike
2016-07-20 21:49 ` gregkh [this message]
2016-07-20 22:46 ` Marciniszyn, Mike
2016-07-27 13:59 ` Marciniszyn, Mike
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=20160720214912.GA14708@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.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