From: kernel test robot <lkp@intel.com>
To: Naresh Solanki <naresh.solanki@9elements.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Naresh Solanki <naresh.solanki@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] regulator: event: Add regulator netlink event support
Date: Tue, 21 Nov 2023 16:45:35 +0800 [thread overview]
Message-ID: <202311211612.t2XcssHt-lkp@intel.com> (raw)
In-Reply-To: <20231120194311.3581036-1-naresh.solanki@9elements.com>
Hi Naresh,
kernel test robot noticed the following build errors:
[auto build test ERROR on 753e4d5c433da57da75dd4c3e1aececc8e874a62]
url: https://github.com/intel-lab-lkp/linux/commits/Naresh-Solanki/regulator-event-Add-regulator-netlink-event-support/20231121-034604
base: 753e4d5c433da57da75dd4c3e1aececc8e874a62
patch link: https://lore.kernel.org/r/20231120194311.3581036-1-naresh.solanki%409elements.com
patch subject: [PATCH v1] regulator: event: Add regulator netlink event support
config: loongarch-randconfig-r071-20231121 (https://download.01.org/0day-ci/archive/20231121/202311211612.t2XcssHt-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231121/202311211612.t2XcssHt-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/202311211612.t2XcssHt-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/regulator/event.c:110:5: error: conflicting types for 'reg_generate_netlink_event'; have 'int(const char *, const char *, u8, int)' {aka 'int(const char *, const char *, unsigned char, int)'}
110 | int reg_generate_netlink_event(const char *device_class, const char *bus_id, u8 type, int data)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/regulator/event.c:6:
drivers/regulator/regnl.h:6:5: note: previous declaration of 'reg_generate_netlink_event' with type 'int(const char *, u64)' {aka 'int(const char *, long long unsigned int)'}
6 | int reg_generate_netlink_event(const char *reg_name, u64 event);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/linux/linkage.h:7,
from include/linux/kernel.h:18,
from include/linux/skbuff.h:13,
from include/linux/netlink.h:7,
from include/net/netlink.h:6,
from drivers/regulator/event.c:3:
drivers/regulator/event.c:114:15: error: conflicting types for 'reg_generate_netlink_event'; have 'int(const char *, const char *, u8, int)' {aka 'int(const char *, const char *, unsigned char, int)'}
114 | EXPORT_SYMBOL(reg_generate_netlink_event);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/export.h:74:28: note: in definition of macro '__EXPORT_SYMBOL'
74 | extern typeof(sym) sym; \
| ^~~
include/linux/export.h:86:41: note: in expansion of macro '_EXPORT_SYMBOL'
86 | #define EXPORT_SYMBOL(sym) _EXPORT_SYMBOL(sym, "")
| ^~~~~~~~~~~~~~
drivers/regulator/event.c:114:1: note: in expansion of macro 'EXPORT_SYMBOL'
114 | EXPORT_SYMBOL(reg_generate_netlink_event);
| ^~~~~~~~~~~~~
drivers/regulator/regnl.h:6:5: note: previous declaration of 'reg_generate_netlink_event' with type 'int(const char *, u64)' {aka 'int(const char *, long long unsigned int)'}
6 | int reg_generate_netlink_event(const char *reg_name, u64 event);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +110 drivers/regulator/event.c
108
109 #else
> 110 int reg_generate_netlink_event(const char *device_class, const char *bus_id, u8 type, int data)
111 {
112 return 0;
113 }
114 EXPORT_SYMBOL(reg_generate_netlink_event);
115
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-11-21 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 19:43 [PATCH v1] regulator: event: Add regulator netlink event support Naresh Solanki
2023-11-21 4:30 ` kernel test robot
2023-11-21 5:50 ` kernel test robot
2023-11-21 8:45 ` kernel test robot [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=202311211612.t2XcssHt-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--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