Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: hifn_795x: Remove unused hifn_*_command structs
Date: Sat, 25 May 2024 00:08:40 +0000	[thread overview]
Message-ID: <ZlEsCJyWmIzlby4w@gallifrey> (raw)
In-Reply-To: <20240511145426.226379-1-linux@treblig.org>

* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> 
> Remove 'hifn_mac_command' and 'hifn_comp_command' which are unused.
> They're the same structure as 'hifn_crypt_command' which is used.
> 
> (I was tempted to remove
>    hifn_base_result
>    hifn_comp_result
>    hifn_mac_result and
>    hifn_crypt_result
> which are also unused, but they vary, and perhaps they're telling
> someone in the future what to look at.)
> 
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>

Ping.

> ---
>  drivers/crypto/hifn_795x.c | 17 -----------------
>  1 file changed, 17 deletions(-)
> 
> diff --git a/drivers/crypto/hifn_795x.c b/drivers/crypto/hifn_795x.c
> index b4a4ec35bce05..9259915267454 100644
> --- a/drivers/crypto/hifn_795x.c
> +++ b/drivers/crypto/hifn_795x.c
> @@ -495,16 +495,6 @@ struct hifn_crypt_command {
>  #define	HIFN_CRYPT_CMD_SRCLEN_M		0xc000
>  #define	HIFN_CRYPT_CMD_SRCLEN_S		14
>  
> -/*
> - * Structure to help build up the command data structure.
> - */
> -struct hifn_mac_command {
> -	volatile __le16	masks;
> -	volatile __le16	header_skip;
> -	volatile __le16	source_count;
> -	volatile __le16	reserved;
> -};
> -
>  #define	HIFN_MAC_CMD_ALG_MASK		0x0001
>  #define	HIFN_MAC_CMD_ALG_SHA1		0x0000
>  #define	HIFN_MAC_CMD_ALG_MD5		0x0001
> @@ -526,13 +516,6 @@ struct hifn_mac_command {
>  #define	HIFN_MAC_CMD_POS_IPSEC		0x0200
>  #define	HIFN_MAC_CMD_NEW_KEY		0x0800
>  
> -struct hifn_comp_command {
> -	volatile __le16		masks;
> -	volatile __le16		header_skip;
> -	volatile __le16		source_count;
> -	volatile __le16		reserved;
> -};
> -
>  #define	HIFN_COMP_CMD_SRCLEN_M		0xc000
>  #define	HIFN_COMP_CMD_SRCLEN_S		14
>  #define	HIFN_COMP_CMD_ONE		0x0100	/* must be one */
> -- 
> 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   |_______/

  reply	other threads:[~2024-05-25  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 14:54 [PATCH] crypto: hifn_795x: Remove unused hifn_*_command structs linux
2024-05-25  0:08 ` 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=ZlEsCJyWmIzlby4w@gallifrey \
    --to=linux@treblig.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --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