From: kernel test robot <lkp@intel.com>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
"(open list:LINUX FOR POWERPC \\(32-BIT AND 64-BIT\\))"
<linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] Connecting the SB600's i8259 controller rather in pasemi's pci.c than in pasemi's setup.c.
Date: Fri, 14 Aug 2026 23:42:18 +0800 [thread overview]
Message-ID: <202608142355.4AeDorvg-lkp@intel.com> (raw)
In-Reply-To: <20260701125941.906-2-chzigotzky@xenosoft.de>
Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes linus/master v7.2-rc7 next-20260813]
[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/Christian-Zigotzky/Connecting-the-SB600-s-i8259-controller-rather-in-pasemi-s-pci-c-than-in-pasemi-s-setup-c/20260813-054214
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link: https://lore.kernel.org/r/20260701125941.906-2-chzigotzky%40xenosoft.de
patch subject: [PATCH] Connecting the SB600's i8259 controller rather in pasemi's pci.c than in pasemi's setup.c.
config: powerpc64-randconfig-r052-20260814 (https://download.01.org/0day-ci/archive/20260814/202608142355.4AeDorvg-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260814/202608142355.4AeDorvg-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/202608142355.4AeDorvg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/powerpc/platforms/pasemi/setup.c:217:6: warning: no previous prototype for function 'nemo_init_IRQ' [-Wmissing-prototypes]
217 | void nemo_init_IRQ(void)
| ^
arch/powerpc/platforms/pasemi/setup.c:217:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
217 | void nemo_init_IRQ(void)
| ^
| static
1 warning generated.
vim +/nemo_init_IRQ +217 arch/powerpc/platforms/pasemi/setup.c
216
> 217 void nemo_init_IRQ(void)
218 {
219 struct device_node *np;
220 int gpio_virq;
221 struct mpic *mpic;
222
223 /* Connect the SB600's legacy i8259 controller */
224 np = of_find_node_by_path("/pxp@0,e0000000");
225 i8259_init(np, 0);
226 of_node_put(np);
227
228 gpio_virq = irq_create_mapping(NULL, 3);
229 irq_set_irq_type(gpio_virq, IRQ_TYPE_LEVEL_HIGH);
230 irq_set_chained_handler(gpio_virq, sb600_8259_cascade);
231 mpic_unmask_irq(irq_get_irq_data(gpio_virq));
232
233 mpic = irq_get_chip_data(gpio_virq);
234 irq_set_default_domain(mpic->irqhost);
235 }
236
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-08-14 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 12:59 [PATCH] Connecting the SB600's i8259 controller rather in pasemi's pci.c than in pasemi's setup.c Christian Zigotzky
2026-07-27 13:43 ` Christophe Leroy (CS GROUP)
2026-07-28 12:50 ` Christian Zigotzky
2026-07-31 16:33 ` Christophe Leroy (CS GROUP)
2026-08-14 15:42 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-01 10:54 Christian Zigotzky
2026-07-07 4:31 ` Christian Zigotzky
2026-07-13 16:18 ` Christian Zigotzky
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=202608142355.4AeDorvg-lkp@intel.com \
--to=lkp@intel.com \
--cc=chleroy@kernel.org \
--cc=chzigotzky@xenosoft.de \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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