mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Denis Benato <benato.denis96@gmail.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, hdegoede@redhat.com,
	ilpo.jarvinen@linux.intel.com,
	platform-driver-x86@vger.kernel.org, mario.limonciello@amd.com,
	"Luke D . Jones" <luke@ljones.dev>,
	Denis Benato <benato.denis96@gmail.com>
Subject: Re: [PATCH v9 1/8] platform/x86: asus-wmi: export symbols used for read/write WMI
Date: Mon, 30 Jun 2025 01:08:20 +0800	[thread overview]
Message-ID: <202506300004.OWO7f60c-lkp@intel.com> (raw)
In-Reply-To: <20250629131423.9013-2-benato.denis96@gmail.com>

Hi Denis,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.16-rc3 next-20250627]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Denis-Benato/platform-x86-asus-wmi-export-symbols-used-for-read-write-WMI/20250629-211651
base:   linus/master
patch link:    https://lore.kernel.org/r/20250629131423.9013-2-benato.denis96%40gmail.com
patch subject: [PATCH v9 1/8] platform/x86: asus-wmi: export symbols used for read/write WMI
config: arc-randconfig-002-20250629 (https://download.01.org/0day-ci/archive/20250630/202506300004.OWO7f60c-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250630/202506300004.OWO7f60c-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/202506300004.OWO7f60c-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from drivers/hid/hid-asus.c:29:
>> include/linux/platform_data/x86/asus-wmi.h:187:19: error: redefinition of 'asus_wmi_set_devstate'
     187 | static inline int asus_wmi_set_devstate(u32 dev_id, u32 ctrl_param, u32 *retval)
         |                   ^~~~~~~~~~~~~~~~~~~~~
   include/linux/platform_data/x86/asus-wmi.h:179:19: note: previous definition of 'asus_wmi_set_devstate' with type 'int(u32,  u32,  u32 *)' {aka 'int(unsigned int,  unsigned int,  unsigned int *)'}
     179 | static inline int asus_wmi_set_devstate(u32 dev_id, u32 ctrl_param, u32 *retval)
         |                   ^~~~~~~~~~~~~~~~~~~~~


vim +/asus_wmi_set_devstate +187 include/linux/platform_data/x86/asus-wmi.h

   165	
   166	#if IS_REACHABLE(CONFIG_ASUS_WMI)
   167	void set_ally_mcu_hack(enum asus_ally_mcu_hack status);
   168	void set_ally_mcu_powersave(bool enabled);
   169	int asus_wmi_get_devstate_dsts(u32 dev_id, u32 *retval);
   170	int asus_wmi_set_devstate(u32 dev_id, u32 ctrl_param, u32 *retval);
   171	int asus_wmi_evaluate_method(u32 method_id, u32 arg0, u32 arg1, u32 *retval);
   172	#else
   173	static inline void set_ally_mcu_hack(enum asus_ally_mcu_hack status)
   174	{
   175	}
   176	static inline void set_ally_mcu_powersave(bool enabled)
   177	{
   178	}
   179	static inline int asus_wmi_set_devstate(u32 dev_id, u32 ctrl_param, u32 *retval)
   180	{
   181		return -ENODEV;
   182	}
   183	static inline int asus_wmi_get_devstate_dsts(u32 dev_id, u32 *retval)
   184	{
   185		return -ENODEV;
   186	}
 > 187	static inline int asus_wmi_set_devstate(u32 dev_id, u32 ctrl_param, u32 *retval)
   188	{
   189		return -ENODEV;
   190	}
   191	static inline int asus_wmi_evaluate_method(u32 method_id, u32 arg0, u32 arg1,
   192						   u32 *retval)
   193	{
   194		return -ENODEV;
   195	}
   196	#endif
   197	

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

  reply	other threads:[~2025-06-29 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-29 13:14 [PATCH v9 0/8] platform/x86: Add asus-armoury driver Denis Benato
2025-06-29 13:14 ` [PATCH v9 1/8] platform/x86: asus-wmi: export symbols used for read/write WMI Denis Benato
2025-06-29 17:08   ` kernel test robot [this message]
2025-06-29 13:14 ` [PATCH v9 2/8] platform/x86: asus-armoury: move existing tunings to asus-armoury module Denis Benato
2025-06-29 18:47   ` ALOK TIWARI
2025-06-30 11:49   ` kernel test robot
2025-06-29 13:14 ` [PATCH v9 3/8] platform/x86: asus-armoury: add panel_hd_mode attribute Denis Benato
2025-06-29 13:14 ` [PATCH v9 4/8] platform/x86: asus-armoury: add apu-mem control support Denis Benato
2025-06-29 13:14 ` [PATCH v9 5/8] platform/x86: asus-armoury: add core count control Denis Benato
2025-06-29 13:14 ` [PATCH v9 6/8] platform/x86: asus-armoury: add screen auto-brightness toggle Denis Benato
2025-06-30 10:17   ` kernel test robot
2025-06-29 13:14 ` [PATCH v9 7/8] platform/x86: asus-wmi: deprecate bios features Denis Benato
2025-06-29 13:14 ` [PATCH v9 8/8] platform/x86: asus-armoury: add ppt_* and nv_* tuning knobs Denis Benato

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=202506300004.OWO7f60c-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=benato.denis96@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=mario.limonciello@amd.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=platform-driver-x86@vger.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

all inboxes | Powered by JetHome®