stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: mcgrof@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] test_firmware: fix setting old custom fw path back on exit," failed to apply to 4.16-stable tree
Date: Fri, 11 May 2018 16:17:13 +0100	[thread overview]
Message-ID: <1526051833.6671.27.camel@codethink.co.uk> (raw)
In-Reply-To: <20180506003840.GA13423@kroah.com>

On Sat, 2018-05-05 at 17:38 -0700, Greg KH wrote:
> On Fri, May 04, 2018 at 04:51:36PM +0100, Ben Hutchings wrote:
> > > > On Sun, 2018-04-29 at 14:36 +0200, gregkh@linuxfoundation.org wrote:
> > > The patch below does not apply to the 4.16-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>.
> > 
> > [...]
> > 
> > The attached version should work for 4.4, 4.9, 4.14 and 4.16.
> 
> Thanks, that worked, but:
> 
> > commit 1dc54bb7046d90447fc92e982f90df57eb3bce37 upstream.
> 
> Wrong git commit id :(
> 
> I fixed it and used the correct one.

Sorry about that.

Ben.

> thanks,
> 
> greg k-h
> 
-- 
Ben Hutchings
Software Developer, Codethink Ltd.

      reply	other threads:[~2018-05-11 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 12:36 FAILED: patch "[PATCH] test_firmware: fix setting old custom fw path back on exit," failed to apply to 4.16-stable tree gregkh
2018-05-04 15:51 ` Ben Hutchings
2018-05-06  0:38   ` Greg KH
2018-05-11 15:17     ` Ben Hutchings [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=1526051833.6671.27.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=mcgrof@kernel.org \
    --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).