From: kbuild test robot <lkp@intel.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: kbuild-all@01.org, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Wanpeng Li <wanpeng.li@hotmail.com>,
stable@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH] nohz: Fix possible missing clock reprog after tick soft restart
Date: Fri, 17 Feb 2017 11:22:56 +0800 [thread overview]
Message-ID: <201702171105.es2N01rV%fengguang.wu@intel.com> (raw)
In-Reply-To: <1486485894-29173-1-git-send-email-fweisbec@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Hi Frederic,
[auto build test ERROR on tip/timers/core]
[cannot apply to v4.10-rc8 next-20170216]
[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/Frederic-Weisbecker/nohz-Fix-possible-missing-clock-reprog-after-tick-soft-restart/20170208-013019
config: i386-randconfig-c0-02171046 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/time/tick-sched.c: In function 'tick_nohz_stop_sched_tick':
>> kernel/time/tick-sched.c:732:6: error: 'struct tick_sched' has no member named 'next_tick'
ts->next_tick = 0;
^
vim +732 kernel/time/tick-sched.c
726 if (delta == 0) {
727 tick_nohz_restart(ts, now);
728 /*
729 * Make sure next tick stop doesn't get fooled by past
730 * clock deadline
731 */
> 732 ts->next_tick = 0;
733 goto out;
734 }
735 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 20133 bytes --]
next prev parent reply other threads:[~2017-02-17 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 16:44 Frederic Weisbecker
2017-02-07 20:05 ` Rik van Riel
2017-02-08 1:56 ` Wanpeng Li
2017-02-10 8:45 ` [tip:timers/urgent] tick/nohz: " tip-bot for Frederic Weisbecker
2017-02-17 3:22 ` kbuild test robot [this message]
2017-02-17 5:34 ` [PATCH] nohz: " kbuild test robot
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=201702171105.es2N01rV%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=fweisbec@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wanpeng.li@hotmail.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®