[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <201702171318.NSwE83Gl%fengguang.wu@intel.com>
Date: Fri, 17 Feb 2017 13:34:11 +0800
From: kbuild test robot <lkp@...el.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: kbuild-all@...org, Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Wanpeng Li <wanpeng.li@...mail.com>, stable@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>, Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH] nohz: Fix possible missing clock reprog after tick soft
restart
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: x86_64-kexec (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
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'; did you mean 'last_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
Download attachment ".config.gz" of type "application/gzip" (24438 bytes)
Powered by blists - more mailing lists