From: kernel test robot <lkp@intel.com>
To: "Luke D. Jones" <luke@ljones.dev>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
platform-driver-x86@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com,
corentin.chary@gmail.com, superm1@kernel.org,
"Luke D. Jones" <luke@ljones.dev>
Subject: Re: [PATCH 3/3] platfom/x86: asus-wmi: cleanup after Ally quirk reverts
Date: Sun, 29 Sep 2024 04:56:03 +0800 [thread overview]
Message-ID: <202409290438.IYVkP4i0-lkp@intel.com> (raw)
In-Reply-To: <20240926095344.1291013-4-luke@ljones.dev>
Hi Luke,
kernel test robot noticed the following build warnings:
[auto build test WARNING on amd-pstate/bleeding-edge]
[also build test WARNING on linus/master v6.11 next-20240927]
[cannot apply to amd-pstate/linux-next]
[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-D-Jones/Revert-platform-x86-asus-wmi-ROG-Ally-increase-wait-time-allow-MCU-powersave/20240926-175641
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git bleeding-edge
patch link: https://lore.kernel.org/r/20240926095344.1291013-4-luke%40ljones.dev
patch subject: [PATCH 3/3] platfom/x86: asus-wmi: cleanup after Ally quirk reverts
config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20240929/202409290438.IYVkP4i0-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240929/202409290438.IYVkP4i0-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/202409290438.IYVkP4i0-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/platform/x86/asus-wmi.c:148:35: warning: 'asus_ally_mcu_quirk' defined but not used [-Wunused-const-variable=]
148 | static const struct dmi_system_id asus_ally_mcu_quirk[] = {
| ^~~~~~~~~~~~~~~~~~~
vim +/asus_ally_mcu_quirk +148 drivers/platform/x86/asus-wmi.c
0f0ac158d28ff7 Luke D. Jones 2021-10-24 147
d2dfed310aae07 Luke D. Jones 2024-08-06 @148 static const struct dmi_system_id asus_ally_mcu_quirk[] = {
d2dfed310aae07 Luke D. Jones 2024-08-06 149 {
d2dfed310aae07 Luke D. Jones 2024-08-06 150 .matches = {
d2dfed310aae07 Luke D. Jones 2024-08-06 151 DMI_MATCH(DMI_BOARD_NAME, "RC71L"),
d2dfed310aae07 Luke D. Jones 2024-08-06 152 },
d2dfed310aae07 Luke D. Jones 2024-08-06 153 },
d2dfed310aae07 Luke D. Jones 2024-08-06 154 {
d2dfed310aae07 Luke D. Jones 2024-08-06 155 .matches = {
d2dfed310aae07 Luke D. Jones 2024-08-06 156 DMI_MATCH(DMI_BOARD_NAME, "RC72L"),
d2dfed310aae07 Luke D. Jones 2024-08-06 157 },
d2dfed310aae07 Luke D. Jones 2024-08-06 158 },
d2dfed310aae07 Luke D. Jones 2024-08-06 159 { },
d2dfed310aae07 Luke D. Jones 2024-08-06 160 };
d2dfed310aae07 Luke D. Jones 2024-08-06 161
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-28 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 9:53 [PATCH 0/3] platfom/x86: asus-wmi: revert ROG Ally quirks Luke D. Jones
2024-09-26 9:53 ` [PATCH 1/3] Revert "platform/x86: asus-wmi: ROG Ally increase wait time, allow MCU powersave" Luke D. Jones
2024-09-26 9:53 ` [PATCH 2/3] Revert "platform/x86: asus-wmi: disable USB0 hub on ROG Ally before suspend" Luke D. Jones
2024-09-26 9:53 ` [PATCH 3/3] platfom/x86: asus-wmi: cleanup after Ally quirk reverts Luke D. Jones
2024-09-28 20:56 ` kernel test robot [this message]
2024-09-26 13:36 ` [PATCH 0/3] platfom/x86: asus-wmi: revert ROG Ally quirks Mario Limonciello
2024-10-02 8:12 ` Luke Jones
2024-10-05 14:37 ` Hans de Goede
2024-10-05 19:48 ` Luke Jones
2024-10-05 21:59 ` Hans de Goede
2024-10-08 0:03 ` Luke Jones
2024-10-08 1:53 ` Mario Limonciello
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=202409290438.IYVkP4i0-lkp@intel.com \
--to=lkp@intel.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@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