From: Milan Broz <gmazyland@gmail.com>
To: Sasha Levin <sashal@kernel.org>, linux-integrity@vger.kernel.org
Cc: stable@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Morris <jmorris@namei.org>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] tpm: Fix null pointer dereference on chip register error path
Date: Sat, 15 Jun 2019 08:28:50 +0200 [thread overview]
Message-ID: <251208d1-96f9-1fab-3fee-4a216ff87f5e@gmail.com> (raw)
In-Reply-To: <20190614215635.2D9BD2184E@mail.kernel.org>
On 14/06/2019 23:56, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
It should be only # v5.1+
And seems I also forgot to add some cc for the original patch, sorry.
The referenced patch is here
https://lore.kernel.org/linux-integrity/20190612084210.13562-1-gmazyland@gmail.com/
Milan
next prev parent reply other threads:[~2019-06-15 6:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 8:42 [PATCH] tpm: Fix null pointer dereference on chip register error path Milan Broz
2019-06-12 20:57 ` James Morris
2019-06-14 21:56 ` Sasha Levin
2019-06-15 6:28 ` Milan Broz [this message]
2019-06-28 7:56 ` Milan Broz
2019-07-02 18:37 ` Jarkko Sakkinen
2019-07-03 23:01 ` Jarkko Sakkinen
2019-07-04 7:26 ` [PATCH v2] " Milan Broz
2019-07-08 14:34 ` Jarkko Sakkinen
2019-07-08 14:44 ` Jarkko Sakkinen
2019-07-05 17:52 ` [PATCH] " Jarkko Sakkinen
2019-07-05 21:23 ` Milan Broz
2019-07-08 14:33 ` 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=251208d1-96f9-1fab-3fee-4a216ff87f5e@gmail.com \
--to=gmazyland@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=sashal@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).