From: David Woodhouse <dwmw2@infradead.org>
To: "Mickaël Salaün" <mic@digikod.net>,
"Jarkko Sakkinen" <jarkko@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Snowberg <eric.snowberg@oracle.com>,
Paul Moore <paul@paul-moore.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/1] Explain panic() calls for keyring initialization
Date: Mon, 21 Mar 2022 18:29:40 +0000 [thread overview]
Message-ID: <f595c9c2da606b799f3a8ded9807cb6d892156c5.camel@infradead.org> (raw)
In-Reply-To: <20220321174548.510516-1-mic@digikod.net>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On Mon, 2022-03-21 at 18:45 +0100, Mickaël Salaün wrote:
>
> Mickaël Salaün (1):
> certs: Explain the rational to call panic()
Nit: "rationale". Even in Simplified English, I believe "rational" is a
completely different word.
> certs/blacklist.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Also, isn't it about time we changed this to call it a denylist?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2022-03-21 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:45 Mickaël Salaün
2022-03-21 17:45 ` [PATCH v1 1/1] certs: Explain the rational to call panic() Mickaël Salaün
2022-03-21 18:23 ` Paul Moore
2022-03-21 23:53 ` Jarkko Sakkinen
2022-03-22 10:54 ` Mickaël Salaün
2022-03-22 10:53 ` Mickaël Salaün
2022-03-21 18:29 ` David Woodhouse [this message]
2022-03-22 10:55 ` [PATCH v1 0/1] Explain panic() calls for keyring initialization Mickaël Salaün
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=f595c9c2da606b799f3a8ded9807cb6d892156c5.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=eric.snowberg@oracle.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
/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
all inboxes | Powered by JetHome®