stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: chiu@endlessm.com, drake@endlessm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tpm: self test failure should not cause suspend to fail" failed to apply to 4.4-stable tree
Date: Thu, 26 Apr 2018 19:52:04 +0200	[thread overview]
Message-ID: <20180426175204.GE28091@kroah.com> (raw)
In-Reply-To: <20180425115301.GA5891@kroah.com>

On Wed, Apr 25, 2018 at 01:53:01PM +0200, Greg KH wrote:
> On Wed, Apr 25, 2018 at 02:22:13PM +0300, Jarkko Sakkinen wrote:
> > On Fri, Apr 20, 2018 at 06:19:30PM +0200, gregkh@linuxfoundation.org wrote:
> > > 
> > > The patch below does not apply to the 4.4-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
> > 
> > I applied this on top of v4.4.99 with "git am -3" without conflicts.
> 
> I don't use git am until I apply the patch itself, I rely on patch to
> get things right to start with.  I'll try this in a few days to see if I
> can force it...

Ah, I remember what happened here.  It applies just fine to 4.4.y and
4.9.y, but the build is then broken.  The code needs to change for those
kernels if you want that patch applied.

If so, can you please provide a working backport?

thanks,

greg k-h

  reply	other threads:[~2018-04-26 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 16:19 FAILED: patch "[PATCH] tpm: self test failure should not cause suspend to fail" failed to apply to 4.4-stable tree gregkh
2018-04-25 11:22 ` Jarkko Sakkinen
2018-04-25 11:53   ` Greg KH
2018-04-26 17:52     ` Greg KH [this message]
2018-05-01 11:57       ` Jarkko Sakkinen

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=20180426175204.GE28091@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chiu@endlessm.com \
    --cc=drake@endlessm.com \
    --cc=jarkko.sakkinen@linux.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).