From: David Howells <dhowells@redhat.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: dhowells@redhat.com, Li zeming <zeming@nfschina.com>,
jmorris@namei.org, serge@hallyn.com, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@nfschina.com
Subject: Re: [PATCH] keys/keyctl: Fix typo in string
Date: Thu, 28 Jul 2022 11:13:50 +0100 [thread overview]
Message-ID: <2687696.1659003230@warthog.procyon.org.uk> (raw)
In-Reply-To: <YstqXEPmPV2YUfWN@kernel.org>
Jarkko Sakkinen <jarkko@kernel.org> wrote:
> Please, add
>
> Fixes: d84f4f992cbd ("CRED: Inaugurate COW credentials")
Since it's not a bugfix, I wouldn't put that in. It doesn't need backporting.
David
prev parent reply other threads:[~2022-07-28 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 2:52 [PATCH] keys/keyctl: Fix typo in string Li zeming
2022-07-11 0:10 ` Jarkko Sakkinen
2022-07-28 10:13 ` David Howells [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=2687696.1659003230@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=kernel@nfschina.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=zeming@nfschina.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