From: kernel test robot <lkp@intel.com>
To: Aleksandar Rikalo <arikalo@gmail.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: oe-kbuild-all@lists.linux.dev,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Chao-ying Fu <cfu@wavecomp.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Ungerer <gerg@kernel.org>, Hauke Mehrtens <hauke@hauke-m.de>,
Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
Marc Zyngier <maz@kernel.org>,
Paul Burton <paulburton@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Serge Semin <fancer.lancer@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: [PATCH v5 04/11] irqchip/mips-gic: Support multi-cluster in for_each_online_cpu_gic()
Date: Fri, 12 Jul 2024 12:38:07 +0800 [thread overview]
Message-ID: <202407121224.kUAil6pa-lkp@intel.com> (raw)
In-Reply-To: <20240711082656.1889440-5-arikalo@gmail.com>
Hi Aleksandar,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/irq/core]
[also build test WARNING on tip/timers/core linus/master v6.10-rc7]
[cannot apply to daniel-lezcano/clockevents/next next-20240711]
[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/Aleksandar-Rikalo/MIPS-CPS-Add-a-couple-of-multi-cluster-utility-functions/20240711-164850
base: tip/irq/core
patch link: https://lore.kernel.org/r/20240711082656.1889440-5-arikalo%40gmail.com
patch subject: [PATCH v5 04/11] irqchip/mips-gic: Support multi-cluster in for_each_online_cpu_gic()
config: mips-allnoconfig (https://download.01.org/0day-ci/archive/20240712/202407121224.kUAil6pa-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240712/202407121224.kUAil6pa-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/202407121224.kUAil6pa-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/irqchip/irq-mips-gic.c:102: warning: expecting prototype for for_each_online_cpu_gic(). Prototype was for gic_unlock_cluster() instead
vim +102 drivers/irqchip/irq-mips-gic.c
90
91 /**
92 * for_each_online_cpu_gic() - Iterate over online CPUs, access local registers
93 * @cpu: An integer variable to hold the current CPU number
94 * @gic_lock: A pointer to raw spin lock used as a guard
95 *
96 * Iterate over online CPUs & configure the other/redirect register region to
97 * access each CPUs GIC local register block, which can be accessed from the
98 * loop body using read_gic_vo_*() or write_gic_vo_*() accessor functions or
99 * their derivatives.
100 */
101 static inline void gic_unlock_cluster(void)
> 102 {
103 if (mips_cps_multicluster_cpus())
104 mips_cm_unlock_other();
105 }
106
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-12 4:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 8:26 [PATCH v5 00/11] MIPS: Support I6500 multi-cluster configuration Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 01/11] MIPS: CPS: Add a couple of multi-cluster utility functions Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 02/11] MIPS: GIC: Generate redirect block accessors Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 03/11] irqchip/mips-gic: Introduce for_each_online_cpu_gic() Aleksandar Rikalo
2024-07-11 11:52 ` Thomas Gleixner
2024-07-11 8:26 ` [PATCH v5 04/11] irqchip/mips-gic: Support multi-cluster in for_each_online_cpu_gic() Aleksandar Rikalo
2024-07-12 4:38 ` kernel test robot [this message]
2024-07-11 8:26 ` [PATCH v5 05/11] irqchip/mips-gic: Setup defaults in each cluster Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 06/11] irqchip/mips-gic: Multi-cluster support Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 07/11] clocksource: mips-gic-timer: Always use cluster 0 counter as clocksource Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 08/11] clocksource: mips-gic-timer: Enable counter when CPUs start Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 09/11] MIPS: pm-cps: Use per-CPU variables as per-CPU, not per-core Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 10/11] MIPS: CPS: Introduce struct cluster_boot_config Aleksandar Rikalo
2024-07-11 8:26 ` [PATCH v5 11/11] MIPS: CPS: Boot CPUs in secondary clusters Aleksandar Rikalo
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=202407121224.kUAil6pa-lkp@intel.com \
--to=lkp@intel.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.com \
--cc=cfu@wavecomp.com \
--cc=daniel.lezcano@linaro.org \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.org \
--cc=hauke@hauke-m.de \
--cc=ilya.lipnitskiy@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulburton@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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