From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [tglx-devel:irq/proc 2/16] kernel/irq/proc.c:466:31: sparse: sparse: label 'continue' already bound
Date: Wed, 13 May 2026 02:15:54 +0800 [thread overview]
Message-ID: <202605130239.Js0Zf2Gd-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: kernel/irq/proc.c:466:31: sparse: sparse: label 'continue' already bound"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Thomas Gleixner <tglx@kernel.org>
CC: Dmitry Ilvokhin <d@ilvokhin.com>
CC: Radu Rendec <radu@rendec.net>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git irq/proc
head: 6aa40b910f0486df6146560b14fd0171437f9b9b
commit: 208dfeb6922a76810177278ed8e6e2d65f81a844 [2/16] genirq/proc: Avoid formatting zero counts in /proc/interrupts
:::::: branch date: 10 hours ago
:::::: commit date: 20 hours ago
config: nios2-randconfig-r123-20260512 (https://download.01.org/0day-ci/archive/20260513/202605130239.Js0Zf2Gd-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605130239.Js0Zf2Gd-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/r/202605130239.Js0Zf2Gd-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/irq/proc.c:466:31: sparse: sparse: label 'continue' already bound
>> kernel/irq/proc.c:466:31: sparse: sparse: label 'break' already bound
vim +/continue +466 kernel/irq/proc.c
a6e120ed42004d6 Thomas Gleixner 2011-03-25 452
208dfeb6922a768 Thomas Gleixner 2026-04-01 453 /* Same as seq_put_decimal_ull_width(p, " ", cnt, 10) */
208dfeb6922a768 Thomas Gleixner 2026-04-01 454 #define ZSTR1 " 0"
208dfeb6922a768 Thomas Gleixner 2026-04-01 455 #define ZSTR1_LEN (sizeof(ZSTR1) - 1)
208dfeb6922a768 Thomas Gleixner 2026-04-01 456 #define ZSTR16 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 \
208dfeb6922a768 Thomas Gleixner 2026-04-01 457 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1 ZSTR1
208dfeb6922a768 Thomas Gleixner 2026-04-01 458 #define ZSTR256 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 \
208dfeb6922a768 Thomas Gleixner 2026-04-01 459 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16 ZSTR16
208dfeb6922a768 Thomas Gleixner 2026-04-01 460
208dfeb6922a768 Thomas Gleixner 2026-04-01 461 static inline void irq_proc_emit_zero_counts(struct seq_file *p, unsigned int zeros)
208dfeb6922a768 Thomas Gleixner 2026-04-01 462 {
208dfeb6922a768 Thomas Gleixner 2026-04-01 463 if (!zeros)
208dfeb6922a768 Thomas Gleixner 2026-04-01 464 return;
208dfeb6922a768 Thomas Gleixner 2026-04-01 465
208dfeb6922a768 Thomas Gleixner 2026-04-01 @466 for (unsigned int n = min(zeros, 256); n; zeros -= n, n = min(zeros, 256))
208dfeb6922a768 Thomas Gleixner 2026-04-01 467 seq_write(p, ZSTR256, n * ZSTR1_LEN);
208dfeb6922a768 Thomas Gleixner 2026-04-01 468 }
208dfeb6922a768 Thomas Gleixner 2026-04-01 469
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-12 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202605130239.Js0Zf2Gd-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.