linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: dbasehore@chromium.org
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	dbasehore@chromium.org, linux-pm@vger.kernel.org,
	rjw@rjwysocki.net, pavel@ucw.cz, len.brown@intel.com,
	tglx@linutronix.de, gnomes@lxorguk.ukuu.org.uk,
	peterz@infradead.org
Subject: Re: [PATCH v4 2/5] clockevents: Add timed freeze
Date: Sun, 12 Jun 2016 01:02:45 +0800	[thread overview]
Message-ID: <201606120021.vzBOoe4F%fengguang.wu@intel.com> (raw)
In-Reply-To: <1465506139-25981-3-git-send-email-dbasehore@chromium.org>

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

Hi,

[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.7-rc2 next-20160609]
[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/dbasehore-chromium-org/Add-suspend-to-idle-validation-for-Intel-SoCs/20160610-053246
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-randconfig-h0-06112342 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

>> kernel/time/clockevents.c:403:5: error: redefinition of 'timed_freeze'
    int timed_freeze(struct timed_freeze_ops *ops, void *data, ktime_t delta)
        ^~~~~~~~~~~~
   In file included from kernel/time/clockevents.c:20:0:
   include/linux/suspend.h:291:19: note: previous definition of 'timed_freeze' was here
    static inline int timed_freeze(struct timed_freeze_ops *ops, void *data,
                      ^~~~~~~~~~~~

vim +/timed_freeze +403 kernel/time/clockevents.c

   397	 *
   398	 * Returns the value from ops->enter_freeze or ops->callback on success, -EERROR
   399	 * otherwise. If an error is encountered while setting up the clock event,
   400	 * freeze with still be entered, but it will not be timed nor will the callback
   401	 * function be run.
   402	 */
 > 403	int timed_freeze(struct timed_freeze_ops *ops, void *data, ktime_t delta)
   404	{
   405		int cpu = smp_processor_id();
   406		struct tick_device *td = tick_get_device(cpu);

---
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: 22079 bytes --]

  parent reply	other threads:[~2016-06-11 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 21:02 [PATCH v4 0/5] Add suspend-to-idle validation for Intel SoCs dbasehore
2016-06-09 21:02 ` [PATCH v4 1/5] x86: stub out pmc function dbasehore
2016-06-09 21:02 ` [PATCH v4 2/5] clockevents: Add timed freeze dbasehore
2016-06-09 22:43   ` Thomas Gleixner
2016-06-21  0:12     ` dbasehore .
2016-06-11 17:02   ` kbuild test robot [this message]
2016-06-09 21:02 ` [PATCH v4 3/5] x86, apic: Add timed freeze support dbasehore
2016-06-09 21:02 ` [PATCH v4 4/5] freeze: Add error reporting dbasehore
2016-06-09 21:02 ` [PATCH v4 5/5] intel_idle: Add S0ix validation dbasehore

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=201606120021.vzBOoe4F%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dbasehore@chromium.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=kbuild-all@01.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    /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).