mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dexuan Cui <decui@microsoft.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [PATCH] clocksource: Allow unregistering the watchdog
Date: Sat, 23 Jan 2016 01:15:04 +0800	[thread overview]
Message-ID: <201601230101.aCmyISAp%fengguang.wu@intel.com> (raw)
In-Reply-To: <1453482097-11065-1-git-send-email-vkuznets@redhat.com>

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

Hi Vitaly,

[auto build test ERROR on tip/timers/core]
[also build test ERROR on v4.4 next-20160122]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Vitaly-Kuznetsov/clocksource-Allow-unregistering-the-watchdog/20160123-010529
config: xtensa-allyesconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All errors (new ones prefixed by >>):

   kernel/time/clocksource.c: In function '__clocksource_register_scale':
>> kernel/time/clocksource.c:769:2: error: implicit declaration of function 'clocksource_select_watchdog' [-Werror=implicit-function-declaration]
     clocksource_select_watchdog(false);
     ^
   cc1: some warnings being treated as errors

vim +/clocksource_select_watchdog +769 kernel/time/clocksource.c

   763	
   764		/* Add clocksource to the clocksource list */
   765		mutex_lock(&clocksource_mutex);
   766		clocksource_enqueue(cs);
   767		clocksource_enqueue_watchdog(cs);
   768		clocksource_select();
 > 769		clocksource_select_watchdog(false);
   770		mutex_unlock(&clocksource_mutex);
   771		return 0;
   772	}

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 43387 bytes --]

      reply	other threads:[~2016-01-22 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 17:01 Vitaly Kuznetsov
2016-01-22 17:15 ` kbuild test robot [this message]

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=201601230101.aCmyISAp%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=decui@microsoft.com \
    --cc=john.stultz@linaro.org \
    --cc=kbuild-all@01.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@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

all inboxes | Powered by JetHome®