From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Philipp Stanner <phasta@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v1 2/2] devres: Move devm_alloc_percpu() and related to devres.h
Date: Thu, 13 Nov 2025 12:49:34 +0800 [thread overview]
Message-ID: <202511122250.550UBJAu-lkp@intel.com> (raw)
In-Reply-To: <20251111144104.910241-3-andriy.shevchenko@linux.intel.com>
Hi Andy,
kernel test robot noticed the following build errors:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on driver-core/driver-core-next driver-core/driver-core-linus linus/master v6.18-rc5 next-20251112]
[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/Andy-Shevchenko/devres-Remove-unused-devm_free_percpu/20251111-230827
base: driver-core/driver-core-testing
patch link: https://lore.kernel.org/r/20251111144104.910241-3-andriy.shevchenko%40linux.intel.com
patch subject: [PATCH v1 2/2] devres: Move devm_alloc_percpu() and related to devres.h
config: i386-buildonly-randconfig-004-20251112 (https://download.01.org/0day-ci/archive/20251112/202511122250.550UBJAu-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251112/202511122250.550UBJAu-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/202511122250.550UBJAu-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpio/gpiolib-devres.c:9:
>> include/linux/device/devres.h:113:6: error: variable has incomplete type 'void __attribute__((btf_type_tag("percpu")))' (aka 'void')
113 | void __percpu *__devm_alloc_percpu(struct device *dev, size_t size, size_t align);
| ^
include/linux/compiler_types.h:60:19: note: expanded from macro '__percpu'
60 | # define __percpu __percpu_qual BTF_TYPE_TAG(percpu)
| ^
In file included from drivers/gpio/gpiolib-devres.c:9:
include/linux/device/devres.h:113:14: error: expected ';' after top level declarator
113 | void __percpu *__devm_alloc_percpu(struct device *dev, size_t size, size_t align);
| ^
| ;
2 errors generated.
vim +113 include/linux/device/devres.h
98
99 /**
100 * devm_alloc_percpu - Resource-managed alloc_percpu
101 * @dev: Device to allocate per-cpu memory for
102 * @type: Type to allocate per-cpu memory for
103 *
104 * Managed alloc_percpu. Per-cpu memory allocated with this function is
105 * automatically freed on driver detach.
106 *
107 * RETURNS:
108 * Pointer to allocated memory on success, NULL on failure.
109 */
110 #define devm_alloc_percpu(dev, type) \
111 ((typeof(type) __percpu *)__devm_alloc_percpu((dev), sizeof(type), __alignof__(type)))
112
> 113 void __percpu *__devm_alloc_percpu(struct device *dev, size_t size, size_t align);
114
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-11-13 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 14:39 [PATCH v1 0/2] devres: clean up and move percpu allocator Andy Shevchenko
2025-11-11 14:39 ` [PATCH v1 1/2] devres: Remove unused devm_free_percpu() Andy Shevchenko
2025-11-11 14:58 ` Philipp Stanner
2025-11-11 14:39 ` [PATCH v1 2/2] devres: Move devm_alloc_percpu() and related to devres.h Andy Shevchenko
2025-11-11 16:33 ` kernel test robot
2025-11-13 4:49 ` 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=202511122250.550UBJAu-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=phasta@kernel.org \
--cc=rafael@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