From: kbuild test robot <lkp@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: ebiederm@xmission.com, indranil@chelsio.com,
netdev@vger.kernel.org, nirranjan@chelsio.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
stephen@networkplumber.org, ganeshgr@chelsio.com,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
davem@davemloft.net, viro@zeniv.linux.org.uk
Subject: Re: [PATCH net-next v3 1/3] vmcore: add API to collect hardware dump in second kernel
Date: Sun, 1 Apr 2018 08:32:41 +0800 [thread overview]
Message-ID: <201804010849.ZM0J7PZb%fengguang.wu@intel.com> (raw)
In-Reply-To: <194d1e289b385f2cbd4cb2c2569af93723a9cfb8.1522483891.git.rahul.lakkireddy@chelsio.com>
Hi Rahul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Rahul-Lakkireddy/kernel-add-support-to-collect-hardware-logs-in-crash-recovery-kernel/20180401-060904
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> fs/proc/vmcore.c:1199:5: sparse: symbol '__vmcore_add_device_dump' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-04-01 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 8:50 [PATCH net-next v3 0/3] kernel: add support to collect hardware logs in crash recovery kernel Rahul Lakkireddy
2018-03-31 8:50 ` [PATCH net-next v3 1/3] vmcore: add API to collect hardware dump in second kernel Rahul Lakkireddy
2018-04-01 0:32 ` kbuild test robot [this message]
2018-04-01 0:32 ` [RFC PATCH] vmcore: __vmcore_add_device_dump() can be static kbuild test robot
2018-03-31 8:50 ` [PATCH net-next v3 2/3] vmcore: append device dumps to vmcore as elf notes Rahul Lakkireddy
2018-03-31 8:50 ` [PATCH net-next v3 3/3] cxgb4: collect hardware dump in second kernel Rahul Lakkireddy
2018-04-01 0:15 ` kbuild test robot
2018-04-01 0:19 ` 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=201804010849.ZM0J7PZb%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=kbuild-all@01.org \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=stephen@networkplumber.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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