From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Paul Menzel" <pmenzel@molgen.mpg.de>,
"Mario Limonciello" <mario.limonciello@amd.com>
Cc: <peterhuewe@gmx.de>, <linux-kernel@vger.kernel.org>,
<linux-integrity@vger.kernel.org>, <Jason@zx2c4.com>,
<dragonn@op.pl>
Subject: Re: [PATCH 3/3] tpm: Drop CONFIG_HW_RANDOM_TPM
Date: Thu, 03 Aug 2023 12:03:15 +0300 [thread overview]
Message-ID: <CUISED4NBEZP.1AFVEMEVNIVOU@suppilovahvero> (raw)
In-Reply-To: <dcbf7a17-67e3-d97d-bd18-9b0bd917a6cf@molgen.mpg.de>
On Thu Aug 3, 2023 at 10:22 AM EEST, Paul Menzel wrote:
> Dear Mario,
>
>
> Thank you for the patch.
>
> Am 03.08.23 um 03:50 schrieb Mario Limonciello:
> > As the behavior of whether a TPM is registered for hwrng can be controlled
> > by command line, drop the kernel configuration option.
>
> Shouldn’t this be left in to be able to set the default without having
> to change the Linux kernel command line?
Even if it made sense it is completely urelated to the real-world
issues at hand.
BR, Jarkko
next prev parent reply other threads:[~2023-08-03 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 1:50 [PATCH 0/3] More changes related to TPM RNG handling Mario Limonciello
2023-08-03 1:50 ` [PATCH 1/3] tpm: Add a missing check for TPM_CHIP_FLAG_HWRNG_DISABLED Mario Limonciello
2023-08-03 8:59 ` Jarkko Sakkinen
2023-08-03 11:35 ` Mario Limonciello
2023-08-03 13:50 ` Jason A. Donenfeld
2023-08-04 22:52 ` Jarkko Sakkinen
2023-08-03 1:50 ` [PATCH 2/3] tpm: Add command line for not trusting tpm for RNG Mario Limonciello
2023-08-03 13:42 ` Jason A. Donenfeld
2023-08-03 1:50 ` [PATCH 3/3] tpm: Drop CONFIG_HW_RANDOM_TPM Mario Limonciello
2023-08-03 7:22 ` Paul Menzel
2023-08-03 9:03 ` Jarkko Sakkinen [this message]
2023-08-03 11:45 ` Mario Limonciello
2023-08-03 9:01 ` 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=CUISED4NBEZP.1AFVEMEVNIVOU@suppilovahvero \
--to=jarkko@kernel.org \
--cc=Jason@zx2c4.com \
--cc=dragonn@op.pl \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=peterhuewe@gmx.de \
--cc=pmenzel@molgen.mpg.de \
/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