From: kbuild test robot <lkp@intel.com>
To: LABBE Corentin <clabbe.montjoie@gmail.com>
Cc: kbuild-all@01.org, arnd@arndb.de, gregkh@linuxfoundation.org,
LABBE Corentin <clabbe.montjoie@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] char/nvram: fix style issues
Date: Fri, 20 May 2016 19:17:29 +0800 [thread overview]
Message-ID: <201605201946.tzlwwho5%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446716341-18084-2-git-send-email-clabbe.montjoie@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
Hi,
[auto build test ERROR on char-misc/char-misc-next]
[cannot apply to v4.6 next-20160519]
[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/LABBE-Corentin/char-nvram-set-array-of-const-as-const/20151105-174316
config: i386-defconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: the linux-review/LABBE-Corentin/char-nvram-set-array-of-const-as-const/20151105-174316 HEAD 458f91db725087e7bb91bfad834b304e72ec9a9b builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
drivers/char/nvram.c: In function 'nvram_init':
>> drivers/char/nvram.c:457:3: error: implicit declaration of function 'pri_err' [-Werror=implicit-function-declaration]
pri_err("nvram: can't create /proc/driver/nvram\n");
^~~~~~~
cc1: some warnings being treated as errors
vim +/pri_err +457 drivers/char/nvram.c
451 if (ret) {
452 pr_err("nvram: can't misc_register on minor=%d\n", NVRAM_MINOR);
453 goto out;
454 }
455 ret = nvram_add_proc_fs();
456 if (ret) {
> 457 pri_err("nvram: can't create /proc/driver/nvram\n");
458 goto outmisc;
459 }
460 ret = 0;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23872 bytes --]
prev parent reply other threads:[~2016-05-20 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 9:39 [PATCH 1/2] char/nvram: set array of const as const LABBE Corentin
2015-11-05 9:39 ` [PATCH 2/2] char/nvram: fix style issues LABBE Corentin
2015-11-05 10:57 ` kbuild test robot
2015-11-05 16:41 ` Greg KH
2016-05-20 11:17 ` 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=201605201946.tzlwwho5%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=clabbe.montjoie@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).