From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 8994/9550] io_uring/register.c:553:1: sparse: sparse: Using plain integer as NULL pointer
Date: Thu, 21 Dec 2023 01:08:27 +0800 [thread overview]
Message-ID: <202312210144.vItcGK51-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 20d857259d7d10cd0d5e8b60608455986167cfad
commit: c43203154d8ac579537aa0c7802b77d463b1f53a [8994/9550] io_uring/register: move io_uring_register(2) related code to register.c
config: s390-randconfig-r123-20231220 (https://download.01.org/0day-ci/archive/20231221/202312210144.vItcGK51-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231221/202312210144.vItcGK51-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/202312210144.vItcGK51-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
io_uring/register.c: note: in included file:
include/linux/io_uring_types.h:341:48: sparse: sparse: array of flexible structures
>> io_uring/register.c:553:1: sparse: sparse: Using plain integer as NULL pointer
>> io_uring/register.c:553:1: sparse: sparse: Using plain integer as NULL pointer
vim +553 io_uring/register.c
552
> 553 SYSCALL_DEFINE4(io_uring_register, unsigned int, fd, unsigned int, opcode,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-20 17:10 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=202312210144.vItcGK51-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-mm@kvack.org \
--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