[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201704241606.VlTnAXb4%fengguang.wu@intel.com>
Date: Mon, 24 Apr 2017 16:48:17 +0800
From: kbuild test robot <lkp@...el.com>
To: Baoquan He <bhe@...hat.com>
Cc: kbuild-all@...org, linux-kernel@...r.kernel.org,
keescook@...omium.org, mingo@...nel.org, dave.jiang@...el.com,
dan.j.williams@...el.com, hpa@...or.com, tglx@...utronix.de,
dyoung@...hat.com, Baoquan He <bhe@...hat.com>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
Yinghai Lu <yinghai@...nel.org>, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH v2 1/3] KASLR: Parse all memmap entries in cmdline
Hi Baoquan,
[auto build test WARNING on next-20170421]
[also build test WARNING on v4.11-rc8]
[cannot apply to tip/x86/core linus/master linux/master v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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/Baoquan-He/Handle-memmap-and-mem-kernel-options-in-boot-stage-kaslr/20170424-104809
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> arch/x86/boot/compressed/kaslr.c:78:5: sparse: symbol 'mem_avoid_memmap_index' 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