[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <201804010849.ZM0J7PZb%fengguang.wu@intel.com>
Date: Sun, 1 Apr 2018 08:32:41 +0800
From: kbuild test robot <lkp@...el.com>
To: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
Cc: kbuild-all@...org, netdev@...r.kernel.org,
kexec@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, davem@...emloft.net,
viro@...iv.linux.org.uk, ebiederm@...ssion.com,
stephen@...workplumber.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, ganeshgr@...lsio.com,
nirranjan@...lsio.com, indranil@...lsio.com,
Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
Subject: Re: [PATCH net-next v3 1/3] vmcore: add API to collect hardware dump
in second kernel
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
Powered by blists - more mailing lists