From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: [avpatel:riscv_trace_support_v3 30/49] drivers/firmware/riscv/riscv_sbi_sse.c:720:6-8: ERROR: iterator variable bound on line 719 cannot be NULL
Date: Tue, 24 Feb 2026 20:31:44 +0800 [thread overview]
Message-ID: <202602242019.lkBcb1eW-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
CC: Anup Patel <anup@brainfault.org>
tree: https://github.com/avpatel/linux.git riscv_trace_support_v3
head: cb6e52a5cb2529ad7d25344f6c6eaea3b3b9a13a
commit: ab09840bca500d501650d79239ebbbbfbe1a553f [30/49] riscv: Add functions to register ghes having SSE notification
:::::: branch date: 6 hours ago
:::::: commit date: 7 hours ago
config: riscv-randconfig-r064-20260224 (https://download.01.org/0day-ci/archive/20260224/202602242019.lkBcb1eW-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 15.2.0
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>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202602242019.lkBcb1eW-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/firmware/riscv/riscv_sbi_sse.c:720:6-8: ERROR: iterator variable bound on line 719 cannot be NULL
vim +720 drivers/firmware/riscv/riscv_sbi_sse.c
ab09840bca500d Himanshu Chauhan 2026-01-02 713
ab09840bca500d Himanshu Chauhan 2026-01-02 714 static int sse_ghes_handler(u32 event_num, void *arg, struct pt_regs *regs)
ab09840bca500d Himanshu Chauhan 2026-01-02 715 {
ab09840bca500d Himanshu Chauhan 2026-01-02 716 struct sse_ghes_event_data *ev_data = arg;
ab09840bca500d Himanshu Chauhan 2026-01-02 717 struct sse_ghes_callback *cb = NULL;
ab09840bca500d Himanshu Chauhan 2026-01-02 718
ab09840bca500d Himanshu Chauhan 2026-01-02 @719 list_for_each_entry(cb, &ev_data->callback_list, head) {
ab09840bca500d Himanshu Chauhan 2026-01-02 @720 if (cb && cb->ghes && cb->callback) {
ab09840bca500d Himanshu Chauhan 2026-01-02 721 cb->callback(ev_data->event_num, cb->ghes, regs);
ab09840bca500d Himanshu Chauhan 2026-01-02 722 }
ab09840bca500d Himanshu Chauhan 2026-01-02 723 }
ab09840bca500d Himanshu Chauhan 2026-01-02 724
ab09840bca500d Himanshu Chauhan 2026-01-02 725 return 0;
ab09840bca500d Himanshu Chauhan 2026-01-02 726 }
ab09840bca500d Himanshu Chauhan 2026-01-02 727
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-24 12:32 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=202602242019.lkBcb1eW-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--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.