From: kbuild test robot <fengguang.wu@intel.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [zwisler:mmots_dax_tracepoint 82/143] mm/z3fold.c:270:13: error: 'zhdr' undeclared
Date: Fri, 6 Jan 2017 20:38:15 +0800 [thread overview]
Message-ID: <201701062013.C6m54iV6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git mmots_dax_tracepoint
head: da4c62b5ae469ab971d717cd9a6f7651aabe5ab9
commit: e42ecae156681e85b4020293320585249884ec30 [82/143] z3fold: add kref refcounting
config: x86_64-randconfig-i0-201701 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout e42ecae156681e85b4020293320585249884ec30
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/z3fold.c: In function 'z3fold_create_pool':
>> mm/z3fold.c:270:13: error: 'zhdr' undeclared (first use in this function)
kref_init(&zhdr->refcount);
^
mm/z3fold.c:270:13: note: each undeclared identifier is reported only once for each function it appears in
vim +/zhdr +270 mm/z3fold.c
264 int i;
265
266 pool = kzalloc(sizeof(struct z3fold_pool), gfp);
267 if (!pool)
268 return NULL;
269 spin_lock_init(&pool->lock);
> 270 kref_init(&zhdr->refcount);
271 for_each_unbuddied_list(i, 0)
272 INIT_LIST_HEAD(&pool->unbuddied[i]);
273 INIT_LIST_HEAD(&pool->lru);
---
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: 24923 bytes --]
reply other threads:[~2017-01-06 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201701062013.C6m54iV6%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=vitalywool@gmail.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