linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Ulrich Obergfell <uobergfe@redhat.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Don Zickus <dzickus@redhat.com>,
	Andrew Jones <drjones@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	kbuild-all@01.org
Subject: [mmotm:master 155/172] undefined reference to `watchdog_hardlockup_detector_is_enabled'
Date: Tue, 26 Aug 2014 20:55:44 +0800	[thread overview]
Message-ID: <53fc83d0.eS2Nhff1ydj9/9qj%fengguang.wu@intel.com> (raw)

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   9ff078807eb23bbd93e8a09e4d323b4246a2a414
commit: dd537b4f62ee02ada2c10246b9e82eb20287452b [155/172] kernel/watchdog.c: control hard lockup detection default
config: make ARCH=sparc64 defconfig

All error/warnings:

   kernel/built-in.o: In function `proc_dowatchdog':
>> (.text+0x6a5e0): undefined reference to `watchdog_hardlockup_detector_is_enabled'
   kernel/built-in.o: In function `proc_dowatchdog':
>> (.text+0x6a668): undefined reference to `watchdog_enable_hardlockup_detector'
   kernel/built-in.o: In function `proc_dowatchdog':
>> (.text+0x6a75c): undefined reference to `watchdog_enable_hardlockup_detector'

---
0-DAY kernel build testing backend              Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2014-08-26 12:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53fc83d0.eS2Nhff1ydj9/9qj%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=drjones@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=uobergfe@redhat.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