From: kernel test robot <lkp@intel.com>
To: Saeed Mahameed <saeedm@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, Leon Romanovsky <leon@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: [leon-rdma:rdma-next 57/94] drivers/fwctl/fwctl.mod.c:19:45: error: expected ')' before 'FWCTL'
Date: Wed, 8 Jan 2025 23:32:45 +0800 [thread overview]
Message-ID: <202501082329.2BTEPFMS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git rdma-next
head: c2d45bfd2380e40a4079c162471203c1be90e85c
commit: 7bd476f2facaf3ddc828dc0f331cd0feeceaa7c0 [57/94] fwctl/mlx5: Support for communicating with mlx5 fw
config: sparc-allmodconfig (https://download.01.org/0day-ci/archive/20250108/202501082329.2BTEPFMS-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250108/202501082329.2BTEPFMS-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/202501082329.2BTEPFMS-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/fwctl/fwctl.mod.c:2:
>> drivers/fwctl/fwctl.mod.c:19:45: error: expected ')' before 'FWCTL'
19 | KSYMTAB_FUNC(_fwctl_alloc_device, "_gpl", ""FWCTL"");
| ^~~~~
include/linux/export-internal.h:45:28: note: in definition of macro '__KSYMTAB'
45 | " .asciz \"" ns "\"" "\n" \
| ^~
drivers/fwctl/fwctl.mod.c:19:1: note: in expansion of macro 'KSYMTAB_FUNC'
19 | KSYMTAB_FUNC(_fwctl_alloc_device, "_gpl", ""FWCTL"");
| ^~~~~~~~~~~~
include/linux/export-internal.h:41:12: note: to match this '('
41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \
| ^
include/linux/export-internal.h:62:41: note: in expansion of macro '__KSYMTAB'
62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns)
| ^~~~~~~~~
drivers/fwctl/fwctl.mod.c:19:1: note: in expansion of macro 'KSYMTAB_FUNC'
19 | KSYMTAB_FUNC(_fwctl_alloc_device, "_gpl", ""FWCTL"");
| ^~~~~~~~~~~~
drivers/fwctl/fwctl.mod.c:20:40: error: expected ')' before 'FWCTL'
20 | KSYMTAB_FUNC(fwctl_register, "_gpl", ""FWCTL"");
| ^~~~~
include/linux/export-internal.h:45:28: note: in definition of macro '__KSYMTAB'
45 | " .asciz \"" ns "\"" "\n" \
| ^~
drivers/fwctl/fwctl.mod.c:20:1: note: in expansion of macro 'KSYMTAB_FUNC'
20 | KSYMTAB_FUNC(fwctl_register, "_gpl", ""FWCTL"");
| ^~~~~~~~~~~~
include/linux/export-internal.h:41:12: note: to match this '('
41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \
| ^
include/linux/export-internal.h:62:41: note: in expansion of macro '__KSYMTAB'
62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns)
| ^~~~~~~~~
drivers/fwctl/fwctl.mod.c:20:1: note: in expansion of macro 'KSYMTAB_FUNC'
20 | KSYMTAB_FUNC(fwctl_register, "_gpl", ""FWCTL"");
| ^~~~~~~~~~~~
drivers/fwctl/fwctl.mod.c:21:42: error: expected ')' before 'FWCTL'
21 | KSYMTAB_FUNC(fwctl_unregister, "_gpl", ""FWCTL"");
| ^~~~~
include/linux/export-internal.h:45:28: note: in definition of macro '__KSYMTAB'
45 | " .asciz \"" ns "\"" "\n" \
| ^~
drivers/fwctl/fwctl.mod.c:21:1: note: in expansion of macro 'KSYMTAB_FUNC'
21 | KSYMTAB_FUNC(fwctl_unregister, "_gpl", ""FWCTL"");
| ^~~~~~~~~~~~
include/linux/export-internal.h:41:12: note: to match this '('
41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \
| ^
include/linux/export-internal.h:62:41: note: in expansion of macro '__KSYMTAB'
62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns)
| ^~~~~~~~~
drivers/fwctl/fwctl.mod.c:21:1: note: in expansion of macro 'KSYMTAB_FUNC'
21 | KSYMTAB_FUNC(fwctl_unregister, "_gpl", ""FWCTL"");
| ^~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-08 15:33 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=202501082329.2BTEPFMS-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=saeedm@nvidia.com \
/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.