From: Jarkko Sakkinen <jarkko@kernel.org>
To: Li zeming <zeming@nfschina.com>
Cc: dhowells@redhat.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/keyring: Fix typo in string
Date: Mon, 11 Jul 2022 05:52:58 +0300 [thread overview]
Message-ID: <YsuQihEKR8DC+Pnm@kernel.org> (raw)
In-Reply-To: <20220704025610.3834-1-zeming@nfschina.com>
On Mon, Jul 04, 2022 at 10:56:10AM +0800, Li zeming wrote:
> Remove the repeated ',' from string
>
> Signed-off-by: Li zeming <zeming@nfschina.com>
> ---
> security/keys/keyring.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/security/keys/keyring.c b/security/keys/keyring.c
> index 5e6a90760753..c6c47ca9b57d 100644
> --- a/security/keys/keyring.c
> +++ b/security/keys/keyring.c
> @@ -460,7 +460,7 @@ static int keyring_read_iterator(const void *object, void *data)
> struct keyring_read_iterator_context *ctx = data;
> const struct key *key = keyring_ptr_to_key(object);
>
> - kenter("{%s,%d},,{%zu/%zu}",
> + kenter("{%s,%d},{%zu/%zu}",
> key->type->name, key->serial, ctx->count, ctx->buflen);
>
> if (ctx->count >= ctx->buflen)
> @@ -484,7 +484,7 @@ static long keyring_read(const struct key *keyring,
> struct keyring_read_iterator_context ctx;
> long ret;
>
> - kenter("{%d},,%zu", key_serial(keyring), buflen);
> + kenter("{%d},%zu", key_serial(keyring), buflen);
>
> if (buflen & (sizeof(key_serial_t) - 1))
> return -EINVAL;
> --
> 2.18.2
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
prev parent reply other threads:[~2022-07-11 2:53 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
2022-07-11 2:52 ` Jarkko Sakkinen [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=YsuQihEKR8DC+Pnm@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.