linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Dan Streetman <ddstreet@ieee.org>,
	Yu Zhao <yuzhao@google.com>, Seth Jennings <sjenning@redhat.com>,
	Linux-MM <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Avi Kivity <avi@qumranet.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] hotplug: make register and unregister notifier API symmetric
Date: Mon, 5 Dec 2016 07:08:40 +0100	[thread overview]
Message-ID: <20161205060840.GC30758@dhcp22.suse.cz> (raw)
In-Reply-To: <201612031306.dkl5XlAY%fengguang.wu@intel.com>

On Sat 03-12-16 13:15:42, kbuild test robot wrote:
> Hi Michal,
> 
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.9-rc7 next-20161202]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> 
> url:    https://github.com/0day-ci/linux/commits/Michal-Hocko/hotplug-make-register-and-unregister-notifier-API-symmetric/20161203-114815
> config: i386-randconfig-r0-201648 (attached as .config)
> compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All errors (new ones prefixed by >>):
> 
>    arch/x86/oprofile/built-in.o: In function `nmi_timer_shutdown':
> >> nmi_timer_int.c:(.text+0x238b): undefined reference to `__unregister_cpu_notifier'
>    arch/x86/oprofile/built-in.o: In function `nmi_shutdown':
>    nmi_int.c:(.text+0x2793): undefined reference to `__unregister_cpu_notifier'

Ohh, right. I have missed that unregister functions definitions are
guarded as well. This patch should hopefully be correct finally.
Please note it also exports register/unregister callbacks when
CONFIG_HOTPLUG_CPU is not defined which is not really needed strictly
speaking because those are only used when !MODULE but I would rather
not make the code more complicated. If maintainers prefer I can guard
exports separately of course.
---

  reply	other threads:[~2016-12-05  6:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 21:15 [PATCH v2] zswap: only use CPU notifier when HOTPLUG_CPU=y Yu Zhao
2016-12-02 13:46 ` Michal Hocko
2016-12-02 14:24   ` Dan Streetman
2016-12-02 14:38     ` Michal Hocko
2016-12-02 14:44       ` Michal Hocko
2016-12-02 14:56         ` Dan Streetman
2016-12-02 15:19           ` [PATCH] hotplug: make register and unregister notifier API symmetric Michal Hocko
2016-12-03  5:15             ` kbuild test robot
2016-12-05  6:08               ` Michal Hocko [this message]
2016-12-03  7:18             ` kbuild test robot
2016-12-05 20:59             ` Yu Zhao
2016-12-06  9:30               ` Michal Hocko
2016-12-05 21:11   ` [PATCH v2] zswap: only use CPU notifier when HOTPLUG_CPU=y Yu Zhao
2016-12-07 13:54 [PATCH] hotplug: make register and unregister notifier API symmetric Michal Hocko

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=20161205060840.GC30758@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=avi@qumranet.com \
    --cc=ddstreet@ieee.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=sjenning@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=yuzhao@google.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