From: kbuild test robot <lkp@intel.com>
To: Waiman Long <longman@redhat.com>
Cc: kbuild-all@lists.01.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v4 5/7] locking/lockdep: Track number of zapped lock chains
Date: Fri, 24 Jan 2020 21:18:06 +0800 [thread overview]
Message-ID: <202001242112.MR3PxjB1%lkp@intel.com> (raw)
In-Reply-To: <20200121154009.11993-6-longman@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Hi Waiman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on tip/auto-latest arm-perf/for-next/perf v5.5-rc7 next-20200123]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Waiman-Long/locking-lockdep-Reuse-zapped-chain_hlocks-entries/20200124-085419
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git f5bfdc8e3947a7ae489cf8ae9cfd6b3fb357b952
config: x86_64-randconfig-d001-20200124 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: kernel/locking/lockdep_proc.o: in function `lockdep_stats_show':
>> lockdep_proc.c:(.text+0x3fd): undefined reference to `nr_zapped_lock_chains'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35554 bytes --]
next prev parent reply other threads:[~2020-01-24 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 15:40 [PATCH v4 0/7] locking/lockdep: Reuse zapped chain_hlocks entries Waiman Long
2020-01-21 15:40 ` [PATCH v4 1/7] locking/lockdep: Decrement irq context counters when removing lock chain Waiman Long
2020-01-21 15:40 ` [PATCH v4 2/7] locking/lockdep: Display irq_context names in /proc/lockdep_chains Waiman Long
2020-01-21 15:40 ` [PATCH v4 3/7] locking/lockdep: Track number of zapped classes Waiman Long
2020-01-21 15:40 ` [PATCH v4 4/7] locking/lockdep: Throw away all lock chains with zapped class Waiman Long
2020-01-21 15:40 ` [PATCH v4 5/7] locking/lockdep: Track number of zapped lock chains Waiman Long
2020-01-24 13:18 ` kbuild test robot [this message]
2020-01-24 20:15 ` kbuild test robot
2020-01-21 15:40 ` [PATCH v4 6/7] locking/lockdep: Reuse freed chain_hlocks entries Waiman Long
2020-01-24 11:57 ` kbuild test robot
2020-01-21 15:40 ` [PATCH v4 7/7] locking/lockdep: Add a fast path for chain_hlocks allocation Waiman Long
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=202001242112.MR3PxjB1%lkp@intel.com \
--to=lkp@intel.com \
--cc=bvanassche@acm.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).