From: kernel test robot <lkp@intel.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, linux-riscv@lists.infradead.org
Cc: kbuild-all@lists.01.org, rostedt@goodmis.org, mingo@redhat.com,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
aou@eecs.berkeley.edu, mhiramat@kernel.org, zong.li@sifive.com,
guoren@linux.alibaba.com, Atish Patra <Atish.Patra@wdc.com>
Subject: Re: [PATCH] RISC-V: Don't check text_mutex during stop_machine
Date: Thu, 6 May 2021 20:31:56 +0800 [thread overview]
Message-ID: <202105062035.oZ7CoGMh-lkp@intel.com> (raw)
In-Reply-To: <20210506071041.417854-1-palmer@dabbelt.com>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
Hi Palmer,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on linus/master v5.12 next-20210506]
[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]
url: https://github.com/0day-ci/linux/commits/Palmer-Dabbelt/RISC-V-Don-t-check-text_mutex-during-stop_machine/20210506-151316
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ed8e50800bf4c2d904db9c75408a67085e6cca3d
config: riscv-randconfig-c023-20210506 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/61fc593f7bfbd5a52e0e5ba3a55f02df81df08d5
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Palmer-Dabbelt/RISC-V-Don-t-check-text_mutex-during-stop_machine/20210506-151316
git checkout 61fc593f7bfbd5a52e0e5ba3a55f02df81df08d5
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
riscv32-linux-ld: arch/riscv/kernel/patch.o: in function `patch_insn_write':
>> patch.c:(.text+0x68): undefined reference to `riscv_ftrace_in_stop_machine'
>> riscv32-linux-ld: patch.c:(.text+0x6c): undefined reference to `riscv_ftrace_in_stop_machine'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32694 bytes --]
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-05-06 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 7:10 [PATCH] RISC-V: Don't check text_mutex during stop_machine Palmer Dabbelt
2021-05-06 12:31 ` kernel test robot [this message]
2021-05-06 13:20 ` Steven Rostedt
2021-05-06 13:25 ` Steven Rostedt
2021-05-22 19:32 ` Palmer Dabbelt
2021-05-28 22:21 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2022-03-22 2:23 Palmer Dabbelt
2022-05-01 14:09 ` Changbin Du
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=202105062035.oZ7CoGMh-lkp@intel.com \
--to=lkp@intel.com \
--cc=Atish.Patra@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
--cc=zong.li@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