From: Jarkko Sakkinen <jarkko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
"Jan Dąbroś" <jsd@semihalf.com>,
linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
gregkh@linuxfoundation.org, arnd@arndb.de, rrangel@chromium.org,
timvp@google.com, apronin@google.com, mw@semihalf.com,
upstream@semihalf.com, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] char: tpm: Protect tpm_pm_suspend with locks
Date: Sat, 10 Dec 2022 01:57:05 +0000 [thread overview]
Message-ID: <Y5PnceyKQgBlcEUs@kernel.org> (raw)
In-Reply-To: <6d13f2ba-7598-4522-e0e6-32f1577a2655@suse.cz>
On Thu, Dec 08, 2022 at 11:51:24AM +0100, Vlastimil Babka wrote:
> On 12/8/22 10:23, Jarkko Sakkinen wrote:
> > On Sun, Dec 04, 2022 at 08:14:31PM +0100, Jason A. Donenfeld wrote:
> >> >
> >> > Applied to git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
> >>
> >> Oh thank goodness. You'll send this in for rc8 today?
> >
> > for 6.2-rc1
>
> Linus took it directly to rc8, so it would conflict now.
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.1-rc8&id=23393c6461422df5bf8084a086ada9a7e17dc2ba
Thanks for the remark!
BR, Jarkko
prev parent reply other threads:[~2022-12-10 1:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 19:56 [PATCH v3] char: tpm: Protect tpm_pm_suspend with locks Jason A. Donenfeld
2022-12-02 9:32 ` Thorsten Leemhuis
2022-12-02 9:46 ` Jason A. Donenfeld
2022-12-02 10:09 ` Jan Dąbroś
2022-12-03 10:25 ` Jason A. Donenfeld
2022-12-04 17:06 ` Jarkko Sakkinen
2022-12-04 17:10 ` Jarkko Sakkinen
2022-12-04 19:14 ` Jason A. Donenfeld
2022-12-08 9:23 ` Jarkko Sakkinen
2022-12-08 10:51 ` Vlastimil Babka
2022-12-10 1:57 ` 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=Y5PnceyKQgBlcEUs@kernel.org \
--to=jarkko@kernel.org \
--cc=Jason@zx2c4.com \
--cc=apronin@google.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=jsd@semihalf.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=peterhuewe@gmx.de \
--cc=rrangel@chromium.org \
--cc=stable@vger.kernel.org \
--cc=timvp@google.com \
--cc=upstream@semihalf.com \
--cc=vbabka@suse.cz \
/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).