From: kernel test robot <lkp@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2] crypto: rsa-pkcs1pad: export rsa1_asn_lookup()
Date: Thu, 16 May 2024 13:24:20 +0800 [thread overview]
Message-ID: <202405161355.B776iHbb-lkp@intel.com> (raw)
In-Reply-To: <20240515150213.32491-1-jarkko@kernel.org>
Hi Jarkko,
kernel test robot noticed the following build warnings:
[auto build test WARNING on herbert-cryptodev-2.6/master]
[also build test WARNING on herbert-crypto-2.6/master linus/master v6.9 next-20240515]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jarkko-Sakkinen/crypto-rsa-pkcs1pad-export-rsa1_asn_lookup/20240515-230406
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
patch link: https://lore.kernel.org/r/20240515150213.32491-1-jarkko%40kernel.org
patch subject: [PATCH v2] crypto: rsa-pkcs1pad: export rsa1_asn_lookup()
config: i386-buildonly-randconfig-002-20240516 (https://download.01.org/0day-ci/archive/20240516/202405161355.B776iHbb-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240516/202405161355.B776iHbb-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/202405161355.B776iHbb-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> crypto/rsa-pkcs1pad.c:108: warning: Function parameter or struct member 'name' not described in 'rsa_lookup_asn1'
vim +108 crypto/rsa-pkcs1pad.c
a49de377e051ea Tadeusz Struk 2016-03-03 100
446115366ec712 Jarkko Sakkinen 2024-05-15 101 /**
446115366ec712 Jarkko Sakkinen 2024-05-15 102 * rsa_lookup_asn1() - Lookup the ASN.1 digest info given the hash
446115366ec712 Jarkko Sakkinen 2024-05-15 103 * name: hash algorithm name
446115366ec712 Jarkko Sakkinen 2024-05-15 104 *
446115366ec712 Jarkko Sakkinen 2024-05-15 105 * Returns the ASN.1 digest info on success, and NULL on failure.
446115366ec712 Jarkko Sakkinen 2024-05-15 106 */
446115366ec712 Jarkko Sakkinen 2024-05-15 107 const struct rsa_asn1_template *rsa_lookup_asn1(const char *name)
a49de377e051ea Tadeusz Struk 2016-03-03 @108 {
a49de377e051ea Tadeusz Struk 2016-03-03 109 const struct rsa_asn1_template *p;
a49de377e051ea Tadeusz Struk 2016-03-03 110
a49de377e051ea Tadeusz Struk 2016-03-03 111 for (p = rsa_asn1_templates; p->name; p++)
a49de377e051ea Tadeusz Struk 2016-03-03 112 if (strcmp(name, p->name) == 0)
a49de377e051ea Tadeusz Struk 2016-03-03 113 return p;
a49de377e051ea Tadeusz Struk 2016-03-03 114 return NULL;
a49de377e051ea Tadeusz Struk 2016-03-03 115 }
446115366ec712 Jarkko Sakkinen 2024-05-15 116 EXPORT_SYMBOL_GPL(rsa_lookup_asn1);
a49de377e051ea Tadeusz Struk 2016-03-03 117
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-05-16 5:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240515150213.32491-1-jarkko@kernel.org>]
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=202405161355.B776iHbb-lkp@intel.com \
--to=lkp@intel.com \
--cc=jarkko@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox