From: kernel test robot <lkp@intel.com>
To: "Rusydi H. Makarim" <rusydi.makarim@kriptograf.id>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Eric Biggers <ebiggers@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
"Rusydi H. Makarim" <rusydi.makarim@kriptograf.id>
Subject: Re: [PATCH 1/3] lib/crypto: Add KUnit test vectors for Ascon-Hash256
Date: Mon, 22 Dec 2025 18:11:48 +0100 [thread overview]
Message-ID: <202512221855.nLchuL2R-lkp@intel.com> (raw)
In-Reply-To: <20251215-ascon_hash256-v1-1-24ae735e571e@kriptograf.id>
Hi Rusydi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 92de2d349e02c2dd96d8d1b7016cc78cf80fc085]
url: https://github.com/intel-lab-lkp/linux/commits/Rusydi-H-Makarim/lib-crypto-Add-KUnit-test-vectors-for-Ascon-Hash256/20251215-215114
base: 92de2d349e02c2dd96d8d1b7016cc78cf80fc085
patch link: https://lore.kernel.org/r/20251215-ascon_hash256-v1-1-24ae735e571e%40kriptograf.id
patch subject: [PATCH 1/3] lib/crypto: Add KUnit test vectors for Ascon-Hash256
config: x86_64-rhel-9.4-kunit (https://download.01.org/0day-ci/archive/20251222/202512221855.nLchuL2R-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251222/202512221855.nLchuL2R-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/202512221855.nLchuL2R-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from lib/crypto/tests/ascon_hash_kunit.c:6:
>> include/crypto/ascon_hash.h:24:18: warning: 'ascon_p_rndc' defined but not used [-Wunused-const-variable=]
24 | static const u64 ascon_p_rndc[] = {
| ^~~~~~~~~~~~
vim +/ascon_p_rndc +24 include/crypto/ascon_hash.h
18
19 /*
20 * The standard of Ascon permutation in NIST SP 800-232 specifies 16 round
21 * constants to accomodate potential functionality extensions in the future
22 * (see page 2).
23 */
> 24 static const u64 ascon_p_rndc[] = {
25 0x000000000000003cULL, 0x000000000000002dULL, 0x000000000000001eULL,
26 0x000000000000000fULL, 0x00000000000000f0ULL, 0x00000000000000e1ULL,
27 0x00000000000000d2ULL, 0x00000000000000c3ULL, 0x00000000000000b4ULL,
28 0x00000000000000a5ULL, 0x0000000000000096ULL, 0x0000000000000087ULL,
29 0x0000000000000078ULL, 0x0000000000000069ULL, 0x000000000000005aULL,
30 0x000000000000004bULL,
31 };
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-22 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251215-ascon_hash256-v1-1-24ae735e571e@kriptograf.id>
2025-12-19 4:29 ` [PATCH 1/3] lib/crypto: Add KUnit test vectors for Ascon-Hash256 kernel test robot
2025-12-22 17:11 ` kernel test robot [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=202512221855.nLchuL2R-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rusydi.makarim@kriptograf.id \
/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;
as well as URLs for NNTP newsgroup(s).