From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: jesper.nilsson@axis.com, lars.persson@axis.com
Cc: herbert@gondor.apana.org.au, linux-arm-kernel@axis.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: acix: Remove unused struct 'dbgfs_u32'
Date: Sat, 25 May 2024 00:06:31 +0000 [thread overview]
Message-ID: <ZlErh687UaEjCkIV@gallifrey> (raw)
In-Reply-To: <20240511145017.226166-1-linux@treblig.org>
* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> 'dbgfs_u32' appears unused.
> Remove it.
> (pdma_stat_descr is also unused, but I'm assuming it's
> some useful layout description of firmware/hardware
> so best left in)
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
Ping.
Dave
> ---
> drivers/crypto/axis/artpec6_crypto.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/crypto/axis/artpec6_crypto.c b/drivers/crypto/axis/artpec6_crypto.c
> index dbc1d483f2afa..75440ea6206e2 100644
> --- a/drivers/crypto/axis/artpec6_crypto.c
> +++ b/drivers/crypto/axis/artpec6_crypto.c
> @@ -2811,13 +2811,6 @@ static struct aead_alg aead_algos[] = {
>
> #ifdef CONFIG_DEBUG_FS
>
> -struct dbgfs_u32 {
> - char *name;
> - mode_t mode;
> - u32 *flag;
> - char *desc;
> -};
> -
> static struct dentry *dbgfs_root;
>
> static void artpec6_crypto_init_debugfs(void)
> --
> 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:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 14:50 [PATCH] crypto: acix: Remove unused struct 'dbgfs_u32' linux
2024-05-25 0:06 ` Dr. David Alan Gilbert [this message]
2024-05-31 7:48 ` Jesper Nilsson
2024-05-31 9:41 ` 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=ZlErh687UaEjCkIV@gallifrey \
--to=dave@treblig.org \
--cc=herbert@gondor.apana.org.au \
--cc=jesper.nilsson@axis.com \
--cc=lars.persson@axis.com \
--cc=linux-arm-kernel@axis.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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