All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [ardb:arm64-fpsimd-on-stack2 19/19] lib/test_fpu_glue.c:28:2: error: too few arguments to function call, expected 1, have 0
Date: Thu, 2 Oct 2025 14:52:25 +0800	[thread overview]
Message-ID: <202510021400.SOpdrxp9-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git arm64-fpsimd-on-stack2
head:   b5e76712d12bee6396a6232e659ea7f10758e48b
commit: b5e76712d12bee6396a6232e659ea7f10758e48b [19/19] arm64/fpsimd: Allocate kernel mode FP/SIMD buffers on the stack
config: arm64-randconfig-002-20251002 (https://download.01.org/0day-ci/archive/20251002/202510021400.SOpdrxp9-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 39f292ffa13d7ca0d1edff27ac8fd55024bb4d19)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251002/202510021400.SOpdrxp9-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/202510021400.SOpdrxp9-lkp@intel.com/

All errors (new ones prefixed by >>):

>> lib/test_fpu_glue.c:28:2: error: too few arguments to function call, expected 1, have 0
      28 |         kernel_fpu_begin();
         |         ^~~~~~~~~~~~~~~~~~
   arch/arm64/include/asm/fpu.h:12:46: note: expanded from macro 'kernel_fpu_begin'
      12 | #define kernel_fpu_begin()      kernel_neon_begin()
         |                                 ~~~~~~~~~~~~~~~~~ ^
   arch/arm64/include/asm/neon.h:16:6: note: 'kernel_neon_begin' declared here
      16 | void kernel_neon_begin(struct user_fpsimd_state *);
         |      ^                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
   lib/test_fpu_glue.c:30:2: error: too few arguments to function call, expected 1, have 0
      30 |         kernel_fpu_end();
         |         ^~~~~~~~~~~~~~~~
   arch/arm64/include/asm/fpu.h:13:42: note: expanded from macro 'kernel_fpu_end'
      13 | #define kernel_fpu_end()        kernel_neon_end()
         |                                 ~~~~~~~~~~~~~~~ ^
   arch/arm64/include/asm/neon.h:17:6: note: 'kernel_neon_end' declared here
      17 | void kernel_neon_end(struct user_fpsimd_state *);
         |      ^               ~~~~~~~~~~~~~~~~~~~~~~~~~~
   2 errors generated.


vim +28 lib/test_fpu_glue.c

4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  23  
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  24  static int test_fpu_get(void *data, u64 *val)
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  25  {
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  26  	int status = -EINVAL;
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  27  
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18 @28  	kernel_fpu_begin();
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  29  	status = test_fpu();
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  30  	kernel_fpu_end();
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  31  
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  32  	*val = 1;
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  33  	return status;
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  34  }
4185b3b92792ea lib/test_fpu.c Petteri Aimonen 2020-06-18  35  

:::::: The code at line 28 was first introduced by commit
:::::: 4185b3b92792eaec5869266e594338343421ffb0 selftests/fpu: Add an FPU selftest

:::::: TO: Petteri Aimonen <jpa@git.mail.kapsi.fi>
:::::: CC: Borislav Petkov <bp@suse.de>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-10-02  6: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=202510021400.SOpdrxp9-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.