From: kbuild test robot <lkp@intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: kbuild-all@01.org, Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v3 2/2] pstore/ram: Set pstore flags dynamically
Date: Fri, 22 Jul 2016 07:07:19 +0800 [thread overview]
Message-ID: <201607220759.UdkqVToh%fengguang.wu@intel.com> (raw)
In-Reply-To: <1469062758-1190-2-git-send-email-namhyung@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
Hi,
[auto build test ERROR on ia64/next]
[also build test ERROR on v4.7-rc7]
[cannot apply to next-20160721]
[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/Namhyung-Kim/pstore-Split-pstore-fragile-flags/20160722-060839
base: https://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git next
config: x86_64-randconfig-i0-201629 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
fs/pstore/ram.c: In function 'ramoops_probe':
>> fs/pstore/ram.c:543:6: error: 'ctx' undeclared (first use in this function)
if (ctx->console_size)
^
fs/pstore/ram.c:543:6: note: each undeclared identifier is reported only once for each function it appears in
>> fs/pstore/ram.c:544:24: error: 'PSTORE_FLAGS_CONOLE' undeclared (first use in this function)
cxt->pstore.flags |= PSTORE_FLAGS_CONOLE;
^
vim +/ctx +543 fs/pstore/ram.c
537 pr_err("cannot allocate pstore buffer\n");
538 err = -ENOMEM;
539 goto fail_clear;
540 }
541
542 cxt->pstore.flags = PSTORE_FLAGS_DMESG;
> 543 if (ctx->console_size)
> 544 cxt->pstore.flags |= PSTORE_FLAGS_CONOLE;
545 if (ctx->ftrace_size)
546 cxt->pstore.flags |= PSTORE_FLAGS_FTRACE;
547 if (ctx->pmsg_size)
---
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: 30002 bytes --]
next prev parent reply other threads:[~2016-07-21 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 0:59 [PATCH v3 1/2] pstore: Split pstore fragile flags Namhyung Kim
2016-07-21 0:59 ` [PATCH v3 2/2] pstore/ram: Set pstore flags dynamically Namhyung Kim
2016-07-21 23:07 ` kbuild test robot [this message]
2016-07-22 0:17 ` kbuild test robot
2016-07-22 13:45 ` [PATCH v3.1 " Namhyung Kim
2016-09-08 20:37 ` Kees Cook
2016-09-09 5:56 ` Namhyung Kim
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=201607220759.UdkqVToh%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®