From: kernel test robot <lkp@intel.com>
To: Charlie Jenkins <charlie@rivosinc.com>,
linux-riscv@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Charlie Jenkins <charlie@rivosinc.com>
Subject: Re: [PATCH v2 2/2] riscv: Add tests for riscv module loading
Date: Tue, 10 Oct 2023 23:04:58 +0800 [thread overview]
Message-ID: <202310102243.0Ab0xH1g-lkp@intel.com> (raw)
In-Reply-To: <20231006-module_relocations-v2-2-47566453fedc@rivosinc.com>
Hi Charlie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 82714078aee4ccbd6ee7579d5a21f8a72155d0fb]
url: https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins/riscv-Add-remaining-module-relocations/20231007-084330
base: 82714078aee4ccbd6ee7579d5a21f8a72155d0fb
patch link: https://lore.kernel.org/r/20231006-module_relocations-v2-2-47566453fedc%40rivosinc.com
patch subject: [PATCH v2 2/2] riscv: Add tests for riscv module loading
config: riscv-randconfig-002-20231010 (https://download.01.org/0day-ci/archive/20231010/202310102243.0Ab0xH1g-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231010/202310102243.0Ab0xH1g-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/202310102243.0Ab0xH1g-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/riscv/kernel/tests/module_test/test_module_linking_main.c:26:6: warning: no previous prototype for 'run_test_set' [-Wmissing-prototypes]
26 | void run_test_set(struct kunit *test)
| ^~~~~~~~~~~~
>> arch/riscv/kernel/tests/module_test/test_module_linking_main.c:39:6: warning: no previous prototype for 'run_test_sub' [-Wmissing-prototypes]
39 | void run_test_sub(struct kunit *test)
| ^~~~~~~~~~~~
>> arch/riscv/kernel/tests/module_test/test_module_linking_main.c:54:6: warning: no previous prototype for 'run_test_uleb' [-Wmissing-prototypes]
54 | void run_test_uleb(struct kunit *test)
| ^~~~~~~~~~~~~
vim +/run_test_set +26 arch/riscv/kernel/tests/module_test/test_module_linking_main.c
25
> 26 void run_test_set(struct kunit *test)
27 {
28 int val32 = test_set32();
29 int val16 = test_set16();
30 int val8 = test_set8();
31 int val6 = test_set6();
32
33 CHECK_EQ(val32, 0);
34 CHECK_EQ(val16, 0);
35 CHECK_EQ(val8, 0);
36 CHECK_EQ(val6, 0);
37 }
38
> 39 void run_test_sub(struct kunit *test)
40 {
41 int val64 = test_sub64();
42 int val32 = test_sub32();
43 int val16 = test_sub16();
44 int val8 = test_sub8();
45 int val6 = test_sub6();
46
47 CHECK_EQ(val64, 0);
48 CHECK_EQ(val32, 0);
49 CHECK_EQ(val16, 0);
50 CHECK_EQ(val8, 0);
51 CHECK_EQ(val6, 0);
52 }
53
> 54 void run_test_uleb(struct kunit *test)
55 {
56 int valuleb = test_uleb();
57
58 CHECK_EQ(valuleb, 0);
59 }
60
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-10-10 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 0:41 [PATCH v2 0/2] riscv: Add remaining module relocations and tests Charlie Jenkins
2023-10-07 0:41 ` [PATCH v2 1/2] riscv: Add remaining module relocations Charlie Jenkins
2023-10-07 0:41 ` [PATCH v2 2/2] riscv: Add tests for riscv module loading Charlie Jenkins
2023-10-10 15:04 ` kernel test robot [this message]
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=202310102243.0Ab0xH1g-lkp@intel.com \
--to=lkp@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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;
as well as URLs for NNTP newsgroup(s).