From: David Howells <dhowells@redhat.com>
To: linux@treblig.org
Cc: dhowells@redhat.com, herbert@gondor.apana.org.au,
davem@davemloft.net, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: asymmetric_keys - Remove unused key_being_used_for[]
Date: Mon, 20 Jan 2025 09:34:31 +0000 [thread overview]
Message-ID: <988301.1737365671@warthog.procyon.org.uk> (raw)
In-Reply-To: <20250112163059.467573-1-linux@treblig.org>
linux@treblig.org wrote:
> key_being_used_for[] is an unused array of textual names for
> the elements of the enum key_being_used_for. It was added in 2015 by
> commit 99db44350672 ("PKCS#7: Appropriately restrict authenticated
> attributes and content type")
>
> Remove it.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2025-01-20 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 16:30 [PATCH] crypto: asymmetric_keys - Remove unused key_being_used_for[] linux
2025-01-19 4:47 ` Herbert Xu
2025-01-20 9:34 ` 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=988301.1737365671@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
/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