From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>
Subject: Re: [PATCH v2 0/2] fixes for v4.4
Date: Mon, 4 Jun 2018 23:00:43 +0300 [thread overview]
Message-ID: <20180604200043.GF2691@linux.intel.com> (raw)
In-Reply-To: <20180602131858.GF31493@kroah.com>
On Sat, Jun 02, 2018 at 03:18:58PM +0200, Greg KH wrote:
> On Wed, May 30, 2018 at 11:44:38PM +0300, Jarkko Sakkinen wrote:
> > Decided to add Enric's commit because it is also a bug fix instead
> > of modifying Chris commit.
>
> Why just 4.4 and not also 4.9? I don't want to take patches that would
> cause a regression for people moving from 4.4 to 4.9, so can you also
> provide 4.9 backports of this? If so, I will be glad to queue up both
> sets of patches.
Yes, I can do this. I'll check the v4.4 change with the original author
as I have to put the check in the original patch into different place
before sending anything (I do not have any POWER systes available to
test it myself).
/Jarkko
prev parent reply other threads:[~2018-06-04 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 20:44 [PATCH v2 0/2] fixes for v4.4 Jarkko Sakkinen
2018-05-30 20:44 ` Jarkko Sakkinen
2018-05-30 20:44 ` [PATCH v2 1/2] tpm: do not suspend/resume if power stays on Jarkko Sakkinen
2018-05-30 20:44 ` Jarkko Sakkinen
2018-05-30 23:56 ` Jarkko Sakkinen
2018-05-30 20:44 ` [PATCH v2 2/2] tpm: self test failure should not cause suspend to fail Jarkko Sakkinen
2018-05-30 20:44 ` Jarkko Sakkinen
2018-05-30 20:44 ` Jarkko Sakkinen
2018-06-02 13:18 ` [PATCH v2 0/2] fixes for v4.4 Greg KH
2018-06-04 20:00 ` Jarkko Sakkinen [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=20180604200043.GF2691@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.