From: kbuild test robot <lkp@intel.com>
To: Karim Eshapa <karim.eshapa@gmail.com>
Cc: kbuild-all@01.org, hubcap@omnibond.com,
linux-kernel@vger.kernel.org,
Karim Eshapa <karim.eshapa@gmail.com>
Subject: Re: [PATCH] fs:orangefs:orangefs-debug.h: Use ARRAY_SIZE kernel macro
Date: Thu, 20 Apr 2017 13:07:29 +0800 [thread overview]
Message-ID: <201704201239.Rx0mdbIl%fengguang.wu@intel.com> (raw)
In-Reply-To: <1492649982-15418-1-git-send-email-karim.eshapa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2938 bytes --]
Hi Karim,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc7 next-20170419]
[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/Karim-Eshapa/fs-orangefs-orangefs-debug-h-Use-ARRAY_SIZE-kernel-macro/20170420-105518
config: x86_64-randconfig-i0-201716 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
In file included from fs/orangefs/orangefs-debug.h:15:0,
from fs/orangefs/protocol.h:336,
from fs/orangefs/acl.c:7:
fs/orangefs/orangefs-kernel.h: In function 'is_root_handle':
>> fs/orangefs/orangefs-kernel.h:365:2: error: implicit declaration of function 'gossip_debug' [-Werror=implicit-function-declaration]
gossip_debug(GOSSIP_DCACHE_DEBUG,
^
>> fs/orangefs/orangefs-kernel.h:365:15: error: 'GOSSIP_DCACHE_DEBUG' undeclared (first use in this function)
gossip_debug(GOSSIP_DCACHE_DEBUG,
^
fs/orangefs/orangefs-kernel.h:365:15: note: each undeclared identifier is reported only once for each function it appears in
fs/orangefs/orangefs-kernel.h: In function 'match_handle':
fs/orangefs/orangefs-kernel.h:381:15: error: 'GOSSIP_DCACHE_DEBUG' undeclared (first use in this function)
gossip_debug(GOSSIP_DCACHE_DEBUG,
^
cc1: some warnings being treated as errors
vim +/gossip_debug +365 fs/orangefs/orangefs-kernel.h
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 359 {
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 360 return get_ino_from_khandle(dentry->d_parent->d_inode);
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 361 }
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 362
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 363 static inline int is_root_handle(struct inode *inode)
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 364 {
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 @365 gossip_debug(GOSSIP_DCACHE_DEBUG,
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 366 "%s: root handle: %pU, this handle: %pU:\n",
f7ab093f fs/orangefs/pvfs2-kernel.h Mike Marshall 2015-07-17 367 __func__,
8bb8aefd fs/orangefs/pvfs2-kernel.h Yi Liu 2015-11-24 368 &ORANGEFS_SB(inode->i_sb)->root_khandle,
:::::: The code at line 365 was first introduced by commit
:::::: f7ab093f74bf638ed98fd1115f3efa17e308bb7f Orangefs: kernel client part 1
:::::: TO: Mike Marshall <hubcap@omnibond.com>
:::::: CC: Mike Marshall <hubcap@omnibond.com>
---
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: 24019 bytes --]
next prev parent reply other threads:[~2017-04-20 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 0:59 Karim Eshapa
2017-04-20 5:07 ` kbuild test robot [this message]
2017-04-20 13:04 ` [PATCH] fs:orangefs:orangefs-debug, orangefs-kernel: Fixing warning issues and use ARRAY_SIZE Karim Eshapa
2017-04-20 17:20 ` kbuild test robot
2017-04-20 17:25 ` kbuild test robot
2017-04-20 7:17 ` [PATCH] fs:orangefs:orangefs-debug.h: Use ARRAY_SIZE kernel macro kbuild test robot
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=201704201239.Rx0mdbIl%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hubcap@omnibond.com \
--cc=karim.eshapa@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®