From: Pratyush Yadav <pratyush@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
kexec@lists.infradead.org
Subject: Re: [liveupdate:next 11/21] kernel/liveupdate/luo_session.c:344:48: error: too few arguments provided to function-like macro invocation
Date: Mon, 01 Jun 2026 13:57:19 +0200 [thread overview]
Message-ID: <2vxzcxyah3s0.fsf@kernel.org> (raw)
In-Reply-To: <2vxzik82h40h.fsf@kernel.org> (Pratyush Yadav's message of "Mon, 01 Jun 2026 13:52:14 +0200")
On Mon, Jun 01 2026, Pratyush Yadav wrote:
> On Mon, Jun 01 2026, kernel test robot wrote:
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git next
>> head: f4b4f5fe58a55a4212a263d9d44416778ca6e7a7
>> commit: 74cab0be9a5d9d91471c4dee7311dcdfc1c0a6f4 [11/21] liveupdate: validate session type before performing operation
>> config: x86_64-buildonly-randconfig-003-20260601 (https://download.01.org/0day-ci/archive/20260601/202606011344.RHiYuqso-lkp@intel.com/config)
>> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260601/202606011344.RHiYuqso-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/202606011344.RHiYuqso-lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>>>> kernel/liveupdate/luo_session.c:344:48: error: too few arguments provided to function-like macro invocation
>> 344 | struct liveupdate_session_retrieve_fd, token),
>> | ^
>> kernel/liveupdate/luo_session.c:327:9: note: macro 'IOCTL_OP' defined here
>> 327 | #define IOCTL_OP(_ioctl, _fn, _struct, _last, _type) \
>> | ^
>>>> kernel/liveupdate/luo_session.c:343:2: error: use of undeclared identifier 'IOCTL_OP'
>> 343 | IOCTL_OP(LIVEUPDATE_SESSION_RETRIEVE_FD, luo_session_retrieve_fd,
>> | ^
>>>> kernel/liveupdate/luo_session.c:378:6: error: invalid application of 'sizeof' to an incomplete type 'const struct luo_ioctl_op[]'
>> 378 | ARRAY_SIZE(luo_session_ioctl_ops)) {
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/array_size.h:11:32: note: expanded from macro 'ARRAY_SIZE'
>> 11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
>> | ^~~~~
>> 3 errors generated.
>
> This happens because the patch got moved from the fixes branch to next,
> and next has a new ioctl. Will send a fixup soon.
Nevermind. Seems like this is already fixed (thanks to Mike I think?).
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-06-01 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 5:25 [liveupdate:next 11/21] kernel/liveupdate/luo_session.c:344:48: error: too few arguments provided to function-like macro invocation kernel test robot
2026-06-01 11:52 ` Pratyush Yadav
2026-06-01 11:57 ` Pratyush Yadav [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=2vxzcxyah3s0.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
/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