[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151123084325.4f0b4d62@gandalf.local.home>
Date: Mon, 23 Nov 2015 08:43:25 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: kbuild test robot <lkp@...el.com>
Cc: jianchuan.wang@...driver.com, kbuild-all@...org,
bigeasy@...utronix.de, tglx@...utronix.de, yang.shi@...driver.com,
linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] locking_selftest: Save/restore migrate_disable_atomic
in locking selftest
On Mon, 23 Nov 2015 15:30:30 +0800
kbuild test robot <lkp@...el.com> wrote:
> Hi Jianchuan,
>
> [auto build test ERROR on: v4.4-rc2]
> [also build test ERROR on: next-20151120]
>
> url: https://github.com/0day-ci/linux/commits/jianchuan-wang-windriver-com/locking_selftest-Save-restore-migrate_disable_atomic-in-locking-selftest/20151123-152217
> config: x86_64-randconfig-x013-11230343 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> lib/locking-selftest.c: In function 'dotest':
> >> lib/locking-selftest.c:981:25: error: 'struct task_struct' has no member named 'migrate_disable_atomic'
> save_migrate_atomic = p->migrate_disable_atomic;
> ^
> lib/locking-selftest.c:987:3: error: 'struct task_struct' has no member named 'migrate_disable_atomic'
> p->migrate_disable_atomic = save_migrate_atomic;
> ^
Need to add RT in the subject like "[PATCH RT]". Then perhaps Fengguang
can have his tests either ignore these or test against the -rt trees.
-- Steve
>
> vim +981 lib/locking-selftest.c
>
> 975 int save_migrate_atomic;
> 976 #endif
> 977
> 978 WARN_ON(irqs_disabled());
> 979
> 980 #ifdef CONFIG_SCHED_DEBUG
> > 981 save_migrate_atomic = p->migrate_disable_atomic;
> 982 #endif
> 983
> 984 testcase_fn();
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists