All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
Cc: oe-kbuild-all@lists.linux.dev, Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_sbi_dbtr_v2 62/62] breakpoint_test_riscv.c:126:1: warning: non-void function does not return a value in all control paths
Date: Tue, 03 Feb 2026 23:11:32 +0100	[thread overview]
Message-ID: <202602032303.tUShEdfv-lkp@intel.com> (raw)

tree:   https://github.com/avpatel/linux.git riscv_sbi_dbtr_v2
head:   922a4bdf735544d2054881e7a06eefbeaf243aac
commit: 922a4bdf735544d2054881e7a06eefbeaf243aac [62/62] riscv: Add breakpoint and watchpoint test for riscv
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260203/202602032303.tUShEdfv-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260203/202602032303.tUShEdfv-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/202602032303.tUShEdfv-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> breakpoint_test_riscv.c:126:1: warning: non-void function does not return a value in all control paths [-Wreturn-type]
     126 | }
         | ^
   breakpoint_test_riscv.c:151:1: warning: non-void function does not return a value in all control paths [-Wreturn-type]
     151 | }
         | ^
   2 warnings generated.

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-02-03 22:11 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=202602032303.tUShEdfv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anup@brainfault.org \
    --cc=himanshu.chauhan@oss.qualcomm.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 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.