Hi Jason, [auto build test ERROR on tip/locking/core] [also build test ERROR on v4.8-rc3 next-20160823] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/Avoid-mutex-starvation-when-optimistic-spinning-is-disabled/20160823-161801 config: x86_64-randconfig-x013-201634 (attached as .config) compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): kernel/locking/mutex.c: In function '__mutex_lock_common': >> kernel/locking/mutex.c:638:7: error: 'struct mutex' has no member named 'yield_to_waiter' lock->yield_to_waiter = false; ^~ vim +638 kernel/locking/mutex.c 632 /* set it to 0 if there are no waiters left: */ 633 if (likely(list_empty(&lock->wait_list))) 634 atomic_set(&lock->count, 0); 635 debug_mutex_free_waiter(&waiter); 636 637 if (yield_forced) > 638 lock->yield_to_waiter = false; 639 640 skip_wait: 641 /* got the lock - cleanup and rejoice! */ --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
Attachment:
.config.gz
Description: Binary data
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
