public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: kbuild-all@lists.01.org, Jonas Bonn <jonas@southpole.se>,
	kernel-janitors@vger.kernel.org,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>,
	openrisc@lists.librecores.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] openrisc: use mmgrab
Date: Mon, 30 Dec 2019 12:49:19 +0800	[thread overview]
Message-ID: <201912301238.xfn6pKut%lkp@intel.com> (raw)
In-Reply-To: <1577634178-22530-5-git-send-email-Julia.Lawall@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]

Hi Julia,

I love your patch! Yet something to improve:

[auto build test ERROR on vfio/next]
[also build test ERROR on char-misc/char-misc-testing v5.5-rc3 next-20191220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Julia-Lawall/use-mmgrab/20191230-011611
base:   https://github.com/awilliam/linux-vfio.git next
config: openrisc-simple_smp_defconfig (attached as .config)
compiler: or1k-linux-gcc (GCC) 9.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=9.2.0 make.cross ARCH=openrisc 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/openrisc/kernel/smp.c: In function 'secondary_start_kernel':
>> arch/openrisc/kernel/smp.c:116:2: error: implicit declaration of function 'mmgrab'; did you mean 'igrab'? [-Werror=implicit-function-declaration]
     116 |  mmgrab(mm);
         |  ^~~~~~
         |  igrab
   cc1: some warnings being treated as errors

vim +116 arch/openrisc/kernel/smp.c

   107	
   108	asmlinkage __init void secondary_start_kernel(void)
   109	{
   110		struct mm_struct *mm = &init_mm;
   111		unsigned int cpu = smp_processor_id();
   112		/*
   113		 * All kernel threads share the same mm context; grab a
   114		 * reference and switch to it.
   115		 */
 > 116		mmgrab(mm);
   117		current->active_mm = mm;
   118		cpumask_set_cpu(cpu, mm_cpumask(mm));
   119	
   120		pr_info("CPU%u: Booted secondary processor\n", cpu);
   121	
   122		setup_cpuinfo();
   123		openrisc_clockevent_init();
   124	
   125		notify_cpu_starting(cpu);
   126	
   127		/*
   128		 * OK, now it's safe to let the boot CPU continue
   129		 */
   130		complete(&cpu_running);
   131	
   132		synchronise_count_slave(cpu);
   133		set_cpu_online(cpu, true);
   134	
   135		local_irq_enable();
   136	
   137		preempt_disable();
   138		/*
   139		 * OK, it's off to the idle thread for us
   140		 */
   141		cpu_startup_entry(CPUHP_AP_ONLINE_IDLE);
   142	}
   143	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 7983 bytes --]

  reply	other threads:[~2019-12-30  4:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-29 15:42 [PATCH 0/4] use mmgrab Julia Lawall
2019-12-29 15:42 ` [PATCH 1/4] misc: cxl: " Julia Lawall
2019-12-29 22:38   ` Andrew Donnellan
2020-01-29  5:17   ` Michael Ellerman
2019-12-29 15:42 ` [PATCH 2/4] vfio: vfio_pci_nvlink2: " Julia Lawall
2020-01-06 23:05   ` Alex Williamson
2020-01-07  5:51     ` Dan Carpenter
2020-01-07 17:00     ` Julia Lawall
2020-01-07 17:10       ` Alex Williamson
2020-01-07  9:14   ` Cornelia Huck
2019-12-29 15:42 ` [PATCH 3/4] vfio/spapr_tce: " Julia Lawall
2020-01-06 23:05   ` Alex Williamson
2020-01-07  9:14   ` Cornelia Huck
2019-12-29 15:42 ` [PATCH 4/4] openrisc: " Julia Lawall
2019-12-30  4:49   ` kbuild test robot [this message]
2020-01-06 14:53     ` Stafford Horne
2020-01-31 13:25     ` Stafford Horne
2020-01-03 12:31 ` [PATCH 0/4] " Dan Carpenter
2020-01-03 12:47   ` Julia Lawall

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=201912301238.xfn6pKut%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Julia.Lawall@inria.fr \
    --cc=jonas@southpole.se \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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