All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Harsha Harsha <harsha.harsha@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
	Michal Simek <monstr@monstr.eu>
Subject: [xilinx-xlnx:xlnx_rebase_v6.6_LTS 995/995] drivers/crypto/xilinx/xilinx-ecdsa.c:294:38: warning: variable 'drv_ctx' set but not used
Date: Mon, 29 Apr 2024 22:38:07 +0800	[thread overview]
Message-ID: <202404292212.9O2pZC6T-lkp@intel.com> (raw)

tree:   https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.6_LTS
head:   3af4295e00efdced3e8c6973606a7de55f6bf7dc
commit: 3af4295e00efdced3e8c6973606a7de55f6bf7dc [995/995] drivers: crypto: xilinx: Add support for do_one_request
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240429/202404292212.9O2pZC6T-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240429/202404292212.9O2pZC6T-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202404292212.9O2pZC6T-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/crypto/xilinx/xilinx-ecdsa.c: In function 'handle_ecdsa_req':
>> drivers/crypto/xilinx/xilinx-ecdsa.c:294:38: warning: variable 'drv_ctx' set but not used [-Wunused-but-set-variable]
     294 |         struct xilinx_ecdsa_drv_ctx *drv_ctx;
         |                                      ^~~~~~~


vim +/drv_ctx +294 drivers/crypto/xilinx/xilinx-ecdsa.c

   283	
   284	static int handle_ecdsa_req(struct crypto_engine *engine, void *req)
   285	{
   286		struct akcipher_request *areq = container_of(req,
   287							     struct akcipher_request,
   288							     base);
   289		struct crypto_akcipher *akcipher = crypto_akcipher_reqtfm(req);
   290		struct akcipher_alg *cipher_alg = crypto_akcipher_alg(akcipher);
   291		const struct xilinx_ecdsa_tfm_ctx *tfm_ctx = akcipher_tfm_ctx(akcipher);
   292		const struct xilinx_ecdsa_req_ctx *rq_ctx = akcipher_request_ctx(areq);
   293		struct akcipher_request *subreq = akcipher_request_ctx(req);
 > 294		struct xilinx_ecdsa_drv_ctx *drv_ctx;
   295		int err;
   296	
   297		drv_ctx = container_of(cipher_alg, struct xilinx_ecdsa_drv_ctx, alg.base);
   298	
   299		akcipher_request_set_tfm(subreq, tfm_ctx->fbk_cipher);
   300	
   301		akcipher_request_set_callback(subreq, areq->base.flags, NULL, NULL);
   302		akcipher_request_set_crypt(subreq, areq->src, areq->dst,
   303					   areq->src_len, areq->dst_len);
   304	
   305		if (rq_ctx->op == XILINX_ECDSA_ENCRYPT)
   306			err = crypto_akcipher_encrypt(subreq);
   307		else if (rq_ctx->op == XILINX_ECDSA_DECRYPT)
   308			err = crypto_akcipher_decrypt(subreq);
   309		else
   310			err = -EOPNOTSUPP;
   311	
   312		crypto_finalize_akcipher_request(engine, areq, err);
   313	
   314		return 0;
   315	}
   316	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-04-29 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202404292212.9O2pZC6T-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=git@amd.com \
    --cc=harsha.harsha@amd.com \
    --cc=monstr@monstr.eu \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.