From: kbuild test robot <lkp@intel.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: kbuild-all@01.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Tony Luck <tony.luck@gmail.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Mark Salter <msalter@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH 1/2] efi: Iterate over efi->memmap in for_each_efi_memory_desc
Date: Mon, 11 Apr 2016 21:27:08 +0800 [thread overview]
Message-ID: <201604112154.9eO52Kn9%fengguang.wu@intel.com> (raw)
In-Reply-To: <1460379809-18490-2-git-send-email-matt@codeblueprint.co.uk>
[-- Attachment #1: Type: text/plain, Size: 3912 bytes --]
Hi Matt,
[auto build test ERROR on efi/next]
[cannot apply to v4.6-rc3 next-20160411]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Matt-Fleming/efi-Delete-global-memmap-variable/20160411-210837
base: https://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git next
config: ia64-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=ia64
Note: the linux-review/Matt-Fleming/efi-Delete-global-memmap-variable/20160411-210837 HEAD 8fc82e8aa63ce89d26d143cce41530319212f7d8 builds fine.
It only hurts bisectibility.
All error/warnings (new ones prefixed by >>):
drivers/firmware/efi/efi.c: In function 'efi_mem_desc_lookup':
>> drivers/firmware/efi/efi.c:259:31: warning: initialization from incompatible pointer type
struct efi_memory_map *map = &efi.memmap;
^
In file included from drivers/firmware/efi/efi.c:22:0:
drivers/firmware/efi/efi.c: In function 'efi_mem_attributes':
>> include/linux/efi.h:973:37: error: invalid type argument of '->' (have 'struct efi')
for_each_efi_memory_desc_in_map(efi->memmap, md)
^
include/linux/efi.h:962:15: note: in definition of macro 'for_each_efi_memory_desc_in_map'
for ((md) = (m)->map; \
^
>> drivers/firmware/efi/efi.c:628:2: note: in expansion of macro 'for_each_efi_memory_desc'
for_each_efi_memory_desc(md) {
^
>> include/linux/efi.h:973:37: error: invalid type argument of '->' (have 'struct efi')
for_each_efi_memory_desc_in_map(efi->memmap, md)
^
include/linux/efi.h:963:38: note: in definition of macro 'for_each_efi_memory_desc_in_map'
(md) <= (efi_memory_desc_t *)((m)->map_end - (m)->desc_size); \
^
>> drivers/firmware/efi/efi.c:628:2: note: in expansion of macro 'for_each_efi_memory_desc'
for_each_efi_memory_desc(md) {
^
>> include/linux/efi.h:973:37: error: invalid type argument of '->' (have 'struct efi')
for_each_efi_memory_desc_in_map(efi->memmap, md)
^
include/linux/efi.h:963:53: note: in definition of macro 'for_each_efi_memory_desc_in_map'
(md) <= (efi_memory_desc_t *)((m)->map_end - (m)->desc_size); \
^
>> drivers/firmware/efi/efi.c:628:2: note: in expansion of macro 'for_each_efi_memory_desc'
for_each_efi_memory_desc(md) {
^
>> include/linux/efi.h:973:37: error: invalid type argument of '->' (have 'struct efi')
for_each_efi_memory_desc_in_map(efi->memmap, md)
^
include/linux/efi.h:964:30: note: in definition of macro 'for_each_efi_memory_desc_in_map'
(md) = (void *)(md) + (m)->desc_size)
^
>> drivers/firmware/efi/efi.c:628:2: note: in expansion of macro 'for_each_efi_memory_desc'
for_each_efi_memory_desc(md) {
^
vim +973 include/linux/efi.h
967 * for_each_efi_memory_desc - iterate over descriptors in efi->memmap
968 * @md: the efi_memory_desc_t * iterator
969 *
970 * Once the loop finishes @md must not be accessed.
971 */
972 #define for_each_efi_memory_desc(md) \
> 973 for_each_efi_memory_desc_in_map(efi->memmap, md)
974
975 /*
976 * Format an EFI memory descriptor's type and attributes to a user-provided
---
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: 45879 bytes --]
next prev parent reply other threads:[~2016-04-11 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 13:03 [PATCH 0/2] efi: Delete global 'memmap' variable Matt Fleming
2016-04-11 13:03 ` [PATCH 1/2] efi: Iterate over efi->memmap in for_each_efi_memory_desc Matt Fleming
2016-04-11 13:24 ` kbuild test robot
2016-04-11 13:27 ` kbuild test robot [this message]
2016-04-11 13:03 ` [PATCH 2/2] efi: Remove global 'memmap' Matt Fleming
2016-04-11 13:17 ` Ard Biesheuvel
2016-04-12 20:01 ` Matt Fleming
2016-04-13 8:12 ` Ard Biesheuvel
2016-04-13 10:24 ` Matt Fleming
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=201604112154.9eO52Kn9%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=kbuild-all@01.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=msalter@redhat.com \
--cc=tony.luck@gmail.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®