Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: bbrezillon@kernel.org, arno@natisbad.org, schalla@marvell.com
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: octeontxs -: Remove unused function otx_cpt_eng_grp_has_eng_type
Date: Sun, 23 Feb 2025 00:56:04 +0000	[thread overview]
Message-ID: <Z7pyJCvzOmslwmyM@gallifrey> (raw)
In-Reply-To: <20250223005443.86343-1-linux@treblig.org>

NAK - let me unbreak that subject line...

* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> 
> otx_cpt_eng_grp_has_eng_type() was added in 2020 by
> commit d9110b0b01ff ("crypto: marvell - add support for OCTEON TX CPT
> engine")
> but has remained unused.
> 
> Remove it.
> 
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
>  drivers/crypto/marvell/octeontx/otx_cptpf_ucode.c | 11 -----------
>  drivers/crypto/marvell/octeontx/otx_cptpf_ucode.h |  2 --
>  2 files changed, 13 deletions(-)
> 
> diff --git a/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.c b/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.c
> index c4250e5fcf8f..9472798678f9 100644
> --- a/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.c
> +++ b/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.c
> @@ -505,17 +505,6 @@ int otx_cpt_uc_supports_eng_type(struct otx_cpt_ucode *ucode, int eng_type)
>  }
>  EXPORT_SYMBOL_GPL(otx_cpt_uc_supports_eng_type);
>  
> -int otx_cpt_eng_grp_has_eng_type(struct otx_cpt_eng_grp_info *eng_grp,
> -				 int eng_type)
> -{
> -	struct otx_cpt_engs_rsvd *engs;
> -
> -	engs = find_engines_by_type(eng_grp, eng_type);
> -
> -	return (engs != NULL ? 1 : 0);
> -}
> -EXPORT_SYMBOL_GPL(otx_cpt_eng_grp_has_eng_type);
> -
>  static void print_ucode_info(struct otx_cpt_eng_grp_info *eng_grp,
>  			     char *buf, int size)
>  {
> diff --git a/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.h b/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.h
> index 8620ac87a447..df79ee416c0d 100644
> --- a/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.h
> +++ b/drivers/crypto/marvell/octeontx/otx_cptpf_ucode.h
> @@ -174,7 +174,5 @@ int otx_cpt_try_create_default_eng_grps(struct pci_dev *pdev,
>  void otx_cpt_set_eng_grps_is_rdonly(struct otx_cpt_eng_grps *eng_grps,
>  				    bool is_rdonly);
>  int otx_cpt_uc_supports_eng_type(struct otx_cpt_ucode *ucode, int eng_type);
> -int otx_cpt_eng_grp_has_eng_type(struct otx_cpt_eng_grp_info *eng_grp,
> -				 int eng_type);
>  
>  #endif /* __OTX_CPTPF_UCODE_H */
> -- 
> 2.48.1
> 
-- 
 -----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:[~2025-02-23  0:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23  0:54 [PATCH] crypto: octeontxs -: Remove unused function otx_cpt_eng_grp_has_eng_type linux
2025-02-23  0:56 ` Dr. David Alan Gilbert [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=Z7pyJCvzOmslwmyM@gallifrey \
    --to=linux@treblig.org \
    --cc=arno@natisbad.org \
    --cc=bbrezillon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schalla@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox