From: "Luke Jones" <luke@ljones.dev>
To: "kernel test robot" <lkp@intel.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Jiri Kosina" <jikos@kernel.org>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: Re: [PATCH v3 2/2] platform/x86: asus-wmi: Refactor Ally suspend/resume
Date: Thu, 13 Mar 2025 10:57:29 +1300 [thread overview]
Message-ID: <3d8df52d-4338-4235-b1fa-183f39e3c3aa@app.fastmail.com> (raw)
In-Reply-To: <202503081003.gNlKWt4M-lkp@intel.com>
On Sat, 8 Mar 2025, at 3:55 PM, kernel test robot wrote:
> Hi Luke,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on hid/for-next]
> [also build test ERROR on linus/master v6.14-rc5 next-20250307]
> [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/Luke-Jones/hid-asus-check-ROG-Ally-MCU-version-and-warn/20250227-165941
> base: https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git
> for-next
> patch link:
> https://lore.kernel.org/r/20250227085817.1007697-3-luke%40ljones.dev
> patch subject: [PATCH v3 2/2] platform/x86: asus-wmi: Refactor Ally
> suspend/resume
> config: mips-allyesconfig
> (https://download.01.org/0day-ci/archive/20250308/202503081003.gNlKWt4M-lkp@intel.com/config)
> compiler: mips-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build):
> (https://download.01.org/0day-ci/archive/20250308/202503081003.gNlKWt4M-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/202503081003.gNlKWt4M-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: In function 'set_ally_mcu_hack':
>>> include/linux/platform_data/x86/asus-wmi.h:168:16: error: 'return' with a value, in function returning void [-Wreturn-mismatch]
> 168 | return -ENODEV;
> | ^
> include/linux/platform_data/x86/asus-wmi.h:166:20: note: declared
> here
> 166 | static inline void set_ally_mcu_hack(bool enabled)
> | ^~~~~~~~~~~~~~~~~
> include/linux/platform_data/x86/asus-wmi.h: In function
> 'set_ally_mcu_powersave':
> include/linux/platform_data/x86/asus-wmi.h:172:16: error: 'return'
> with a value, in function returning void [-Wreturn-mismatch]
> 172 | return -ENODEV;
> | ^
> include/linux/platform_data/x86/asus-wmi.h:170:20: note: declared
> here
> 170 | static inline void set_ally_mcu_powersave(bool enabled)
> | ^~~~~~~~~~~~~~~~~~~~~~
*Groaning sounds*.
Ilpo/Hans, you guys want me to fix this and submit new series or can this be corrected when pulled in?
There's two more of the same below this.
>
> vim +/return +168 include/linux/platform_data/x86/asus-wmi.h
>
> 159
> 160 #if IS_REACHABLE(CONFIG_ASUS_WMI)
> 161 void set_ally_mcu_hack(bool enabled);
> 162 void set_ally_mcu_powersave(bool enabled);
> 163 int asus_wmi_set_devstate(u32 dev_id, u32 ctrl_param, u32
> *retval);
> 164 int asus_wmi_evaluate_method(u32 method_id, u32 arg0, u32 arg1,
> u32 *retval);
> 165 #else
> 166 static inline void set_ally_mcu_hack(bool enabled)
> 167 {
> > 168 return -ENODEV;
> 169 }
> 170 static inline void set_ally_mcu_powersave(bool enabled)
> 171 {
> 172 return -ENODEV;
> 173 }
> 174 static inline int asus_wmi_set_devstate(u32 dev_id, u32
> ctrl_param, u32 *retval)
> 175 {
> 176 return -ENODEV;
> 177 }
> 178 static inline int asus_wmi_evaluate_method(u32 method_id, u32
> arg0, u32 arg1,
> 179 u32 *retval)
> 180 {
> 181 return -ENODEV;
> 182 }
> 183 #endif
> 184
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-12 21:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 8:58 [PATCH v3 0/2] hid-asus: asus-wmi: refactor Ally suspend/resume Luke Jones
2025-02-27 8:58 ` [PATCH v3 1/2] hid-asus: check ROG Ally MCU version and warn Luke Jones
2025-02-27 8:58 ` [PATCH v3 2/2] platform/x86: asus-wmi: Refactor Ally suspend/resume Luke Jones
2025-03-08 2:55 ` kernel test robot
2025-03-12 21:57 ` Luke Jones [this message]
2025-02-27 14:35 ` [PATCH v3 0/2] hid-asus: asus-wmi: refactor " Mario Limonciello
2025-03-04 20:56 ` Jiri Kosina
2025-03-06 12:58 ` Ilpo Järvinen
-- strict thread matches above, loose matches on Subject: below --
2025-03-21 3:51 Luke Jones
2025-03-21 3:51 ` [PATCH v3 2/2] platform/x86: asus-wmi: Refactor " Luke Jones
2025-03-21 17:12 ` Mario Limonciello
2025-03-21 18:55 ` Antheas Kapenekakis
2025-03-22 0:33 ` Luke D. Jones
2025-03-22 5:07 ` Antheas Kapenekakis
2025-03-22 8:14 ` Luke D. Jones
2025-03-22 8:24 ` Antheas Kapenekakis
2025-03-22 8:49 ` Luke D. Jones
2025-03-22 8:53 ` Antheas Kapenekakis
2025-03-22 9:18 ` Luke D. Jones
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=3d8df52d-4338-4235-b1fa-183f39e3c3aa@app.fastmail.com \
--to=luke@ljones.dev \
--cc=bentiss@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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