From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org,
andreas@gaisler.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: niagara2: Remove unused struct 'n2_skcipher_request_context'
Date: Sat, 25 May 2024 00:09:17 +0000 [thread overview]
Message-ID: <ZlEsLYaoQxZjyyAX@gallifrey> (raw)
In-Reply-To: <20240511145620.226548-1-linux@treblig.org>
* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> 'n2_skcipher_request_context' was added in
> commit 23a6564a6b51 ("crypto: niagara2 - switch to skcipher API")
> but never used.
> Remove it.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
Ping.
Dave
> ---
> drivers/crypto/n2_core.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/crypto/n2_core.c b/drivers/crypto/n2_core.c
> index 59d472cb11e75..251e088a53dff 100644
> --- a/drivers/crypto/n2_core.c
> +++ b/drivers/crypto/n2_core.c
> @@ -720,10 +720,6 @@ static inline struct n2_skcipher_alg *n2_skcipher_alg(struct crypto_skcipher *tf
> return container_of(alg, struct n2_skcipher_alg, skcipher);
> }
>
> -struct n2_skcipher_request_context {
> - struct skcipher_walk walk;
> -};
> -
> static int n2_aes_setkey(struct crypto_skcipher *skcipher, const u8 *key,
> unsigned int keylen)
> {
> --
> 2.45.0
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2024-05-25 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 14:56 [PATCH] crypto: niagara2: Remove unused struct 'n2_skcipher_request_context' linux
2024-05-25 0:09 ` Dr. David Alan Gilbert [this message]
2024-05-31 9:58 ` Herbert Xu
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=ZlEsLYaoQxZjyyAX@gallifrey \
--to=linux@treblig.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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