All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [l1k:spdm-future 18/46] crypto/ecdsa-x962.c:133:16: error: implicit declaration of function 'crypto_digest_size'; did you mean 'crypto_sig_maxsize'?
Date: Mon, 9 Sep 2024 11:48:44 +0800	[thread overview]
Message-ID: <202409091106.Zn1dPy5q-lkp@intel.com> (raw)

tree:   https://github.com/l1k/linux spdm-future
head:   fc9f4270fb1c1618a497f5bc1cf9eef4ac9032d2
commit: 4bea63ccdf35da2dfec51745eff4aedc115296a8 [18/46] crypto: ecdsa - Move X9.62 signature size calculation into template
config: i386-buildonly-randconfig-002-20240909 (https://download.01.org/0day-ci/archive/20240909/202409091106.Zn1dPy5q-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240909/202409091106.Zn1dPy5q-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/202409091106.Zn1dPy5q-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

   crypto/ecdsa-x962.c: In function 'ecdsa_x962_digest_size':
>> crypto/ecdsa-x962.c:133:16: error: implicit declaration of function 'crypto_digest_size'; did you mean 'crypto_sig_maxsize'? [-Werror=implicit-function-declaration]
     133 |         return crypto_digest_size(ctx->child);
         |                ^~~~~~~~~~~~~~~~~~
         |                crypto_sig_maxsize
   cc1: some warnings being treated as errors
--
   crypto/ecdsa.c: In function 'ecdsa_digest_size':
>> crypto/ecdsa.c:180:16: error: 'SHA512_DIGEST_SIZE' undeclared (first use in this function)
     180 |         return SHA512_DIGEST_SIZE;
         |                ^~~~~~~~~~~~~~~~~~
   crypto/ecdsa.c:180:16: note: each undeclared identifier is reported only once for each function it appears in
>> crypto/ecdsa.c:181:1: warning: control reaches end of non-void function [-Wreturn-type]
     181 | }
         | ^


vim +133 crypto/ecdsa-x962.c

   128	
   129	static unsigned int ecdsa_x962_digest_size(struct crypto_sig *tfm)
   130	{
   131		struct ecdsa_x962_ctx *ctx = crypto_sig_ctx(tfm);
   132	
 > 133		return crypto_digest_size(ctx->child);
   134	}
   135	

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

                 reply	other threads:[~2024-09-09  3:49 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=202409091106.Zn1dPy5q-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=lukas@wunner.de \
    --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.