From: David Howells <dhowells@redhat.com>
To: Li zeming <zeming@nfschina.com>
Cc: dhowells@redhat.com, jarkko@kernel.org, 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/keyring: Fix typo in string
Date: Tue, 05 Jul 2022 14:32:15 +0100 [thread overview]
Message-ID: <2217586.1657027935@warthog.procyon.org.uk> (raw)
In-Reply-To: <20220704025610.3834-1-zeming@nfschina.com>
Li zeming <zeming@nfschina.com> wrote:
> - kenter("{%s,%d},,{%zu/%zu}",
> + kenter("{%s,%d},{%zu/%zu}",
> key->type->name, key->serial, ctx->count, ctx->buflen);
This changed, so yes, it can be fixed.
> - kenter("{%d},,%zu", key_serial(keyring), buflen);
> + kenter("{%d},%zu", key_serial(keyring), buflen);
This one's not a typo.
David
next prev parent reply other threads:[~2022-07-05 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 2:56 [PATCH] keys/keyring: Fix typo in string Li zeming
2022-07-05 13:32 ` David Howells [this message]
2022-07-11 2:52 ` 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=2217586.1657027935@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