From: Markus Elfring <Markus.Elfring@web.de>
To: Mario Limonciello <mario.limonciello@amd.com>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
John Allen <john.allen@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Cc: Mario Limonciello <superm1@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: ccp: Use scoped guard for mutex
Date: Sun, 10 Nov 2024 10:25:53 +0100 [thread overview]
Message-ID: <2d828178-c972-461e-973a-6983f3bf095e@web.de> (raw)
In-Reply-To: <20241109020054.3877377-1-superm1@kernel.org>
> Using a scoped guard simplifies the cleanup handling.
Will another imperative wording become helpful for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc6#n94
Regards,
Markus
next prev parent reply other threads:[~2024-11-10 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 2:00 [PATCH] crypto: ccp: Use scoped guard for mutex Mario Limonciello
2024-11-10 9:25 ` Markus Elfring [this message]
2024-11-11 14:28 ` Tom Lendacky
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=2d828178-c972-461e-973a-6983f3bf095e@web.de \
--to=markus.elfring@web.de \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=superm1@kernel.org \
--cc=thomas.lendacky@amd.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