linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Greentime Hu <green.hu@gmail.com>, Nick Hu <nickhu@andestech.com>,
	Vincent Chen <deanbo422@gmail.com>,
	Alan Kao <alankao@andestech.com>, KC <kclin@andestech.com>
Subject: Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'
Date: Wed, 23 Feb 2022 17:53:00 -0800	[thread overview]
Message-ID: <6b11b037-6664-a1c4-1f1b-c542ee3c096e@infradead.org> (raw)
In-Reply-To: <e1db5104-5257-b02d-e7fe-663099c9114e@infradead.org>



On 2/23/22 17:44, Randy Dunlap wrote:
> Hi ktr, bouncing NDS32 maintainer, Andrew, Steven,
> 

[now adding Andrew and Steven!]

> 
> On 2/23/22 16:04, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   196d330d7fb1e7cc0d85641c89ce4602cb36f12e
>> commit: 36b9b19753937a6fe0e591b518d46a1f2efae679 [70/7526] nds32: add a Kconfig symbol for LOCKDEP_SUPPORT
>> config: nds32-randconfig-r023-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240745.3HwmSv5A-lkp@intel.com/config)
>> compiler: nds32le-linux-gcc (GCC) 11.2.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=36b9b19753937a6fe0e591b518d46a1f2efae679
>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>         git fetch --no-tags linux-next master
>>         git checkout 36b9b19753937a6fe0e591b518d46a1f2efae679
>>         # save the config file to linux build tree
>>         mkdir build_dir
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash
>>
>> 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 >>):
>>
>>    nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>>>> (.text+0x12a): undefined reference to `__trace_hardirqs_off'
>>    (.text+0x12a): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
>>    nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
>>    (.text+0xea): undefined reference to `__trace_hardirqs_off'
>>    nds32le-linux-ld: (.text+0xee): undefined reference to `__trace_hardirqs_off'
>>>> nds32le-linux-ld: (.text+0xf2): undefined reference to `__trace_hardirqs_on'
>>    nds32le-linux-ld: (.text+0xf6): undefined reference to `__trace_hardirqs_on'
> 
> I have posted v1 and v2 patches for this problem (as well as other NDS32 patches),
> but the NDS32 maintainer seems to have disappeared.
> 
> v1:  https://lore.kernel.org/lkml/20210928052657.20909-1-rdunlap@infradead.org/
> v2:  https://lore.kernel.org/lkml/20220217191347.13480-1-rdunlap@infradead.org/
> 
> 
> Any takers?
> 
> thanks.

-- 
~Randy


  reply	other threads:[~2022-02-24  1:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  0:04 [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off' kernel test robot
2022-02-24  1:44 ` Randy Dunlap
2022-02-24  1:53   ` Randy Dunlap [this message]
2022-02-24  2:33     ` Steven Rostedt
2022-02-24  2:38       ` Masahiro Yamada
2022-02-24  3:12       ` Randy Dunlap
2022-02-24  3:40         ` Steven Rostedt
2022-02-24  8:38           ` Arnd Bergmann
2022-02-24  9:56             ` Alan Kao
2022-02-24 11:57               ` Arnd Bergmann
2022-02-24 12:09                 ` Arnd Bergmann

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=6b11b037-6664-a1c4-1f1b-c542ee3c096e@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=alankao@andestech.com \
    --cc=deanbo422@gmail.com \
    --cc=green.hu@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kclin@andestech.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=nickhu@andestech.com \
    --cc=rostedt@goodmis.org \
    /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).