From: kernel test robot <lkp@intel.com>
To: Armin Wolf <W_Armin@gmx.de>,
hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, bifangknt@qq.com,
nicokessler@icloud.com, sre@kernel.org, linux-pm@vger.kernel.org,
wse@tuxedocomputers.com
Subject: Re: [PATCH 5/9] platform/x86: uniwill-laptop: Expose raw battery capacity to userspace
Date: Tue, 10 Nov 2026 19:13:33 +0800 [thread overview]
Message-ID: <202611101928.MbCyLNXk-lkp@intel.com> (raw)
In-Reply-To: <20261110001725.851443-6-W_Armin@gmx.de>
Hi Armin,
kernel test robot noticed the following build errors:
[auto build test ERROR on sre-power-supply/for-next]
[also build test ERROR on linus/master v7.4-rc2 next-20261109]
[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/Armin-Wolf/power-supply-core-Add-power_supply_has_property_direct/20261110-010643
base: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
patch link: https://lore.kernel.org/r/20261110001725.851443-6-W_Armin%40gmx.de
patch subject: [PATCH 5/9] platform/x86: uniwill-laptop: Expose raw battery capacity to userspace
config: i386-randconfig-1009-20261110 (https://download.01.org/0day-ci/archive/20261110/202611101928.MbCyLNXk-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261110/202611101928.MbCyLNXk-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/202611101928.MbCyLNXk-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/platform/x86/uniwill/uniwill-acpi.c:2148:3: error: cannot jump from this goto statement to its label
2148 | goto err_remove;
| ^
drivers/platform/x86/uniwill/uniwill-acpi.c:2150:2: note: jump bypasses initialization of variable with __attribute__((cleanup))
2150 | guard(mutex)(&data->battery_lock);
| ^
include/linux/cleanup.h:416:2: note: expanded from macro 'guard'
416 | CLASS(_name, __UNIQUE_ID(guard))
| ^
include/linux/cleanup.h:299:3: note: expanded from macro 'CLASS'
299 | class_##_name##_constructor
| ^
<scratch space>:19:1: note: expanded from here
19 | class_mutex_constructor
| ^
note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
include/linux/compiler_types.h:16:23: note: expanded from macro '__PASTE'
16 | #define __PASTE(a, b) ___PASTE(a, b)
| ^
include/linux/compiler_types.h:15:24: note: expanded from macro '___PASTE'
15 | #define ___PASTE(a, b) a##b
| ^
<scratch space>:25:1: note: expanded from here
25 | __UNIQUE_ID_unlock_362
| ^
drivers/platform/x86/uniwill/uniwill-acpi.c:2150:2: note: jump bypasses initialization of variable with __attribute__((cleanup))
include/linux/cleanup.h:416:15: note: expanded from macro 'guard'
416 | CLASS(_name, __UNIQUE_ID(guard))
| ^
include/linux/compiler.h:165:2: note: expanded from macro '__UNIQUE_ID'
165 | __PASTE(__UNIQUE_ID_, \
| ^
include/linux/compiler_types.h:16:23: note: expanded from macro '__PASTE'
16 | #define __PASTE(a, b) ___PASTE(a, b)
| ^
include/linux/compiler_types.h:15:24: note: expanded from macro '___PASTE'
15 | #define ___PASTE(a, b) a##b
| ^
<scratch space>:13:1: note: expanded from here
13 | __UNIQUE_ID_guard_361
| ^
drivers/platform/x86/uniwill/uniwill-acpi.c:2139:3: error: cannot jump from this goto statement to its label
2139 | goto err_free;
| ^
drivers/platform/x86/uniwill/uniwill-acpi.c:2150:2: note: jump bypasses initialization of variable with __attribute__((cleanup))
2150 | guard(mutex)(&data->battery_lock);
| ^
include/linux/cleanup.h:416:2: note: expanded from macro 'guard'
416 | CLASS(_name, __UNIQUE_ID(guard))
| ^
include/linux/cleanup.h:299:3: note: expanded from macro 'CLASS'
299 | class_##_name##_constructor
| ^
<scratch space>:19:1: note: expanded from here
19 | class_mutex_constructor
| ^
note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
include/linux/compiler_types.h:16:23: note: expanded from macro '__PASTE'
16 | #define __PASTE(a, b) ___PASTE(a, b)
| ^
include/linux/compiler_types.h:15:24: note: expanded from macro '___PASTE'
15 | #define ___PASTE(a, b) a##b
| ^
<scratch space>:25:1: note: expanded from here
25 | __UNIQUE_ID_unlock_362
| ^
drivers/platform/x86/uniwill/uniwill-acpi.c:2150:2: note: jump bypasses initialization of variable with __attribute__((cleanup))
include/linux/cleanup.h:416:15: note: expanded from macro 'guard'
416 | CLASS(_name, __UNIQUE_ID(guard))
| ^
include/linux/compiler.h:165:2: note: expanded from macro '__UNIQUE_ID'
165 | __PASTE(__UNIQUE_ID_, \
| ^
include/linux/compiler_types.h:16:23: note: expanded from macro '__PASTE'
16 | #define __PASTE(a, b) ___PASTE(a, b)
| ^
include/linux/compiler_types.h:15:24: note: expanded from macro '___PASTE'
15 | #define ___PASTE(a, b) a##b
| ^
<scratch space>:13:1: note: expanded from here
13 | __UNIQUE_ID_guard_361
| ^
2 errors generated.
vim +2148 drivers/platform/x86/uniwill/uniwill-acpi.c
2125
2126 static int uniwill_add_battery(struct power_supply *battery, struct acpi_battery_hook *hook)
2127 {
2128 struct uniwill_data *data = container_of(hook, struct uniwill_data, hook);
2129 struct uniwill_battery_entry *entry;
2130 const struct power_supply_ext *ext;
2131 int ret;
2132
2133 entry = kzalloc_obj(*entry);
2134 if (!entry)
2135 return -ENOMEM;
2136
2137 ret = device_create_file(&battery->dev, &data->charge_full_raw_attr);
2138 if (ret < 0)
2139 goto err_free;
2140
2141 if (power_supply_has_property_direct(battery, POWER_SUPPLY_PROP_CYCLE_COUNT))
2142 ext = &data->standard_extension;
2143 else
2144 ext = &data->cycle_count_extension;
2145
2146 ret = power_supply_register_extension(battery, ext, data->dev, data);
2147 if (ret < 0)
> 2148 goto err_remove;
2149
2150 guard(mutex)(&data->battery_lock);
2151
2152 entry->battery = battery;
2153 list_add(&entry->head, &data->batteries);
2154
2155 return 0;
2156
2157 err_remove:
2158 device_remove_file(&battery->dev, &data->charge_full_raw_attr);
2159
2160 err_free:
2161 kfree(entry);
2162
2163 return ret;
2164 }
2165
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-11-10 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 0:06 [PATCH 0/9] platform/x86: uniwill-laptop: Complete battery support Armin Wolf
2026-11-10 0:06 ` [PATCH 1/9] power: supply: core: Add power_supply_has_property_direct() Armin Wolf
2026-11-10 0:06 ` [PATCH 2/9] power: supply: Enable struct power_supply_ext to be construct dynamically Armin Wolf
2026-11-10 0:06 ` [PATCH 3/9] platform/x86: uniwill-laptop: Report battery cycle count Armin Wolf
2026-11-10 0:06 ` [PATCH 4/9] platform/x86: uniwill-laptop: Expose battery health and cycle count on all devices Armin Wolf
2026-11-10 0:06 ` [PATCH 5/9] platform/x86: uniwill-laptop: Expose raw battery capacity to userspace Armin Wolf
2026-11-10 11:13 ` kernel test robot [this message]
2026-11-10 0:06 ` [PATCH 6/9] platform/x86: uniwill-laptop: Mark sysfs attributes as const Armin Wolf
2026-11-10 0:06 ` [PATCH 7/9] platform/x86: uniwill-laptop: Add support for MECHREVO Yilong15Pro Armin Wolf
2026-11-10 0:06 ` [PATCH 8/9] platform/x86: uniwill-laptop: Add MECHREVO JIAOLONG Series-X6xR55xK Armin Wolf
2026-11-10 0:06 ` [PATCH 9/9] platform/x86: uniwill-laptop: Add support for XMG EVO 14 (E25) Armin Wolf
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=202611101928.MbCyLNXk-lkp@intel.com \
--to=lkp@intel.com \
--cc=W_Armin@gmx.de \
--cc=bifangknt@qq.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nicokessler@icloud.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@kernel.org \
--cc=wse@tuxedocomputers.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 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®