From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jonas Witschel <diabonas@gmx.de>
Cc: Thibaut Sautereau <thibaut.sautereau@clip-os.org>,
Tadeusz Struk <tadeusz.struk@intel.com>,
grawity@gmail.com, James.Bottomley@hansenpartnership.com,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v4] tpm: fix an invalid condition in tpm_common_poll
Date: Thu, 2 May 2019 10:22:05 +0300 [thread overview]
Message-ID: <20190502072205.GF14532@linux.intel.com> (raw)
In-Reply-To: <e9cfa3db-42d7-4e1c-a371-2c810f911dab@gmx.de>
On Tue, Apr 23, 2019 at 10:54:47PM +0200, Jonas Witschel wrote:
> On 2019-04-09 15:44, Jarkko Sakkinen wrote:
> > On Mon, Apr 08, 2019 at 02:01:38PM +0200, Thibaut Sautereau wrote:
> >> [...]
> >> What's the status of this patch now? It's needed in linux-5.0.y as TPM
> >> 2.0 support is currently broken with those stable kernels without this
> >> commit.
> >
> > part of a PR.
> >
> > https://lore.kernel.org/linux-integrity/20190329115544.GA27351@linux.intel.com/
>
> It appears that the final version of the patch that was merged to
> Linus's tree [1] does not include the "Cc: stable@vger.kernel.org" tag.
> If I understand correctly, this means that the patch will not be
> automatically included in the -stable tree without further action. Is
> there a specific reason not to apply this patch to 5.0.x, or did the tag
It is my mistake. What I can do is to post it manually to stable.
I promise to do it as soon as it reaches the mainline.
/Jarkko
prev parent reply other threads:[~2019-05-02 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 18:32 [PATCH v4] tpm: fix an invalid condition in tpm_common_poll Tadeusz Struk
2019-03-28 12:34 ` Jarkko Sakkinen
2019-03-28 16:34 ` Tadeusz Struk
2019-04-08 12:01 ` Thibaut Sautereau
2019-04-09 13:44 ` Jarkko Sakkinen
2019-04-23 20:54 ` Jonas Witschel
2019-04-24 0:43 ` Sasha Levin
2019-04-24 7:06 ` Jonas Witschel
2019-05-02 7:22 ` 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=20190502072205.GF14532@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=diabonas@gmx.de \
--cc=grawity@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tadeusz.struk@intel.com \
--cc=thibaut.sautereau@clip-os.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).