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>,
"Sanchez, Sebastian" <sebastian.sanchez@intel.com>
Subject: Re: FAILED: patch "[PATCH] IB/hfi1: Fix hard lockup due to not using save/restore spin" failed to apply to 4.6-stable tree
Date: Wed, 1 Jun 2016 09:14:37 -0700 [thread overview]
Message-ID: <20160601161437.GA9144@kroah.com> (raw)
In-Reply-To: <20160601161102.GB8493@kroah.com>
On Wed, Jun 01, 2016 at 09:11:02AM -0700, gregkh@linuxfoundation.org wrote:
> On Wed, Jun 01, 2016 at 02:42:56PM +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
> >
> > http://marc.info/?l=linux-rdma&m=146479189725973&w=2 has the patch for the old staging location.
>
> Is that what should be used here? If so, can someone forward it on to
> the stable@ address?
Ah, nevermind, didn't realize that you had just done this and that this
was the link to the message, sorry for the noise, I'll take this one :)
thanks,
greg k-h
next prev parent reply other threads:[~2016-06-01 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 20:08 FAILED: patch "[PATCH] IB/hfi1: Fix hard lockup due to not using save/restore spin" failed to apply to 4.6-stable tree gregkh
2016-06-01 13:54 ` Dennis Dalessandro
2016-06-01 14:42 ` Marciniszyn, Mike
2016-06-01 16:11 ` gregkh
2016-06-01 16:14 ` gregkh [this message]
2016-06-01 16:16 ` 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=20160601161437.GA9144@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=mike.marciniszyn@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