From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [hare-nvme:secure-concat.v5 12/16] include/linux/nvme-keyring.h:23:9: error: incompatible integer to pointer conversion returning 'int' from a function with result type 'struct key *'
Date: Thu, 18 Jul 2024 03:52:23 +0800 [thread overview]
Message-ID: <202407180316.d7PG9Cr1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/nvme.git secure-concat.v5
head: 4d58e409712027c1084413a8c31e93af4d148650
commit: 13f334e9641984819a87fa14cfc477a19c372ed4 [12/16] nvme-tcp: request secure channel concatenation
config: i386-buildonly-randconfig-004-20240718 (https://download.01.org/0day-ci/archive/20240718/202407180316.d7PG9Cr1-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/20240718/202407180316.d7PG9Cr1-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/202407180316.d7PG9Cr1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/nvme/host/auth.c:15:
>> include/linux/nvme-keyring.h:23:9: error: incompatible integer to pointer conversion returning 'int' from a function with result type 'struct key *' [-Wint-conversion]
23 | return -ENOTSUPP;
| ^~~~~~~~~
1 error generated.
vim +23 include/linux/nvme-keyring.h
9d77eb52778499 Hannes Reinecke 2023-08-24 19
c85200aaab7f12 Hannes Reinecke 2023-04-19 20 static struct key *nvme_tls_psk_refresh(struct key *keyring, char *hostnqn, char *subnqn,
c85200aaab7f12 Hannes Reinecke 2023-04-19 21 u8 hmac_id, bool generated, u8 *data, size_t data_len, char *digest)
c85200aaab7f12 Hannes Reinecke 2023-04-19 22 {
c85200aaab7f12 Hannes Reinecke 2023-04-19 @23 return -ENOTSUPP;
:::::: The code at line 23 was first introduced by commit
:::::: c85200aaab7f1248dd0142da172df0047ddbb812 nvme-keyring: add nvme_tls_psk_refresh()
:::::: TO: Hannes Reinecke <hare@suse.de>
:::::: CC: Hannes Reinecke <hare@suse.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-17 19:52 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=202407180316.d7PG9Cr1-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@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