From: Feng Tang <feng.tang@linux.alibaba.com>
To: kernel test robot <lkp@intel.com>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
rafael@kernel.org, Danilo Krummrich <dakr@kernel.org>,
oe-kbuild-all@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
David Hildenbrand <david@kernel.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev
Subject: Re: [PATCH v1] arch_topology: Introduce nr_possible_packages
Date: Tue, 26 May 2026 15:02:05 +0800 [thread overview]
Message-ID: <ahVFbd_O1W44lUXd@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <202605161935.1SnObrFu-lkp@intel.com>
On Sat, May 16, 2026 at 07:46:10PM +0800, kernel test robot wrote:
> Hi Feng,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on driver-core/driver-core-testing]
> [also build test WARNING on driver-core/driver-core-next driver-core/driver-core-linus linus/master v7.1-rc3 next-20260508]
> [cannot apply to linux-review/Feng-Tang/arch_topology-Introduce-nr_possible_packages/20260514-094659]
> [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/Feng-Tang/arch_topology-Introduce-nr_possible_packages/20260515-230156
> base: driver-core/driver-core-testing
> patch link: https://lore.kernel.org/r/20260515144435.93035-1-feng.tang%40linux.alibaba.com
> patch subject: [PATCH v1] arch_topology: Introduce nr_possible_packages
> config: parisc-randconfig-r122-20260516 (https://download.01.org/0day-ci/archive/20260516/202605161935.1SnObrFu-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 13.4.0
> sparse: v0.6.5-rc1
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605161935.1SnObrFu-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/202605161935.1SnObrFu-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> drivers/base/arch_topology.c:841:1: sparse: sparse: symbol 'package_id_mask' was not declared. Should it be static?
Thanks for the report! will fix this warning in the next version.
- Feng
>
> vim +/package_id_mask +841 drivers/base/arch_topology.c
>
> 835
> 836 /*
> 837 * Assuming silicon has a sane package ID decoding method to not have
> 838 * an ID bigger than 2047
> 839 */
> 840 #define MAX_PACKAGE_ID 2047
> > 841 DECLARE_BITMAP(package_id_mask, MAX_PACKAGE_ID + 1);
> 842
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-26 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 14:44 Feng Tang
2026-05-16 11:46 ` kernel test robot
2026-05-26 7:02 ` Feng Tang [this message]
2026-05-27 13:53 ` Sudeep Holla
2026-05-28 7:56 ` Feng Tang
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=ahVFbd_O1W44lUXd@U-2FWC9VHC-2323.local \
--to=feng.tang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--cc=dakr@kernel.org \
--cc=david@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=will@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®