From: kbuild test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@01.org, David Howells <dhowells@redhat.com>,
Tina Ruchandani <ruchandani.tina@gmail.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] afs: use random UUID
Date: Thu, 12 Jan 2017 17:27:12 +0800 [thread overview]
Message-ID: <201701121759.ztKtxdqn%fengguang.wu@intel.com> (raw)
In-Reply-To: <4758856.xip1ncPqxp@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Hi Arnd,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc3 next-20170111]
[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/Arnd-Bergmann/afs-use-random-UUID/20170112-153644
config: x86_64-randconfig-in0-01121653 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
fs/afs/main.c: In function 'afs_init':
>> fs/afs/main.c:45:2: error: implicit declaration of function 'generate_random_uuid' [-Werror=implicit-function-declaration]
generate_random_uuid((unsigned char *)&afs_uuid);
^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/generate_random_uuid +45 fs/afs/main.c
39 static int __init afs_init(void)
40 {
41 int ret;
42
43 printk(KERN_INFO "kAFS: Red Hat AFS client v0.1 registering.\n");
44
> 45 generate_random_uuid((unsigned char *)&afs_uuid);
46
47 /* create workqueue */
48 ret = -ENOMEM;
---
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: 22103 bytes --]
prev parent reply other threads:[~2017-01-12 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 13:44 [PATCH] afs: correctly use 64-bit time for UUID Arnd Bergmann
2017-01-11 13:51 ` David Howells
2017-01-11 14:03 ` Arnd Bergmann
2017-01-11 14:47 ` David Howells
2017-01-11 15:55 ` Arnd Bergmann
2017-01-12 9:27 ` kbuild test robot [this message]
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=201701121759.ztKtxdqn%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruchandani.tina@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;
as well as URLs for NNTP newsgroup(s).