From: Greg KH <gregkh@linuxfoundation.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: jsnitsel@redhat.com, stefanb@linux.ibm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tpm/tpm_i2c_atmel: Return -E2BIG when the transfer is" failed to apply to 4.14-stable tree
Date: Wed, 17 Apr 2019 17:35:01 +0200 [thread overview]
Message-ID: <20190417153501.GA16402@kroah.com> (raw)
In-Reply-To: <20190417151356.GA13218@linux.intel.com>
On Wed, Apr 17, 2019 at 06:13:56PM +0300, Jarkko Sakkinen wrote:
> On Thu, Mar 21, 2019 at 11:16:21AM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.14-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
>
> Tried to apply over v4.4.112. It applies and compiles. Also this driver
> is fairly static because it is used only with legacy hardware so you
> would not expect any merge conflicts with it.
It doesn't apply to 4.4 for me:
~/linux/stable/linux-4.4.y $ patch -p1 --dry-run < ../tpm-tpm_i2c_atmel-return-e2big-when-the-transfer-is-incomplete.patch
checking file drivers/char/tpm/tpm_i2c_atmel.c
Hunk #1 FAILED at 69.
1 out of 1 hunk FAILED
So something must have changed :(
Care to provide a working backport?
thanks,
greg k-h
next prev parent reply other threads:[~2019-04-17 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 10:16 FAILED: patch "[PATCH] tpm/tpm_i2c_atmel: Return -E2BIG when the transfer is" failed to apply to 4.14-stable tree gregkh
2019-04-17 15:13 ` Jarkko Sakkinen
2019-04-17 15:35 ` Greg KH [this message]
2019-04-19 10:48 ` 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=20190417153501.GA16402@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jsnitsel@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.ibm.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).