From: kbuild test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Atish Patra <atish.patra@wdc.com>,
Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-efi@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [v3 PATCH 5/5] RISC-V: Add EFI stub support.
Date: Thu, 16 Apr 2020 09:13:42 +0800 [thread overview]
Message-ID: <202004160922.dSCn2sEV%lkp@intel.com> (raw)
In-Reply-To: <20200415195422.19866-6-atish.patra@wdc.com>
[-- Attachment #1: Type: text/plain, Size: 3673 bytes --]
Hi Atish,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on efi/next]
[also build test WARNING on linus/master v5.7-rc1 next-20200415]
[cannot apply to arm/for-next arm64/for-next/core linux/master atish-riscv-linux/topo_v3]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Atish-Patra/Add-UEFI-support-for-RISC-V/20200416-065438
base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
config: riscv-rv32_defconfig (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from include/linux/list.h:9,
from include/linux/preempt.h:11,
from include/linux/spinlock.h:51,
from include/linux/seqlock.h:36,
from include/linux/time.h:6,
from include/linux/efi.h:17,
from drivers/firmware/efi/libstub/riscv-stub.c:10:
drivers/firmware/efi/libstub/riscv-stub.c: In function 'handle_kernel_image':
>> drivers/firmware/efi/libstub/riscv-stub.c:89:17: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
89 | if (IS_ALIGNED((u64)_start, MIN_KIMG_ALIGN)) {
| ^
include/linux/kernel.h:37:30: note: in definition of macro 'IS_ALIGNED'
37 | #define IS_ALIGNED(x, a) (((x) & ((typeof(x))(a) - 1)) == 0)
| ^
>> drivers/firmware/efi/libstub/riscv-stub.c:89:17: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
89 | if (IS_ALIGNED((u64)_start, MIN_KIMG_ALIGN)) {
| ^
include/linux/kernel.h:37:44: note: in definition of macro 'IS_ALIGNED'
37 | #define IS_ALIGNED(x, a) (((x) & ((typeof(x))(a) - 1)) == 0)
| ^
drivers/firmware/efi/libstub/riscv-stub.c:94:17: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
94 | *image_addr = (u64)_start;
| ^
vim +89 drivers/firmware/efi/libstub/riscv-stub.c
69
70 efi_status_t handle_kernel_image(unsigned long *image_addr,
71 unsigned long *image_size,
72 unsigned long *reserve_addr,
73 unsigned long *reserve_size,
74 unsigned long dram_base,
75 efi_loaded_image_t *image)
76 {
77 efi_status_t status;
78 unsigned long kernel_size, kernel_memsize = 0;
79 unsigned long max_alloc_address;
80
81 if (image->image_base != _start)
82 pr_efi_err("FIRMWARE BUG: efi_loaded_image_t::image_base has bogus value\n");
83
84 kernel_size = _edata - _start;
85 kernel_memsize = kernel_size + (_end - _edata);
86 max_alloc_address = round_up(dram_base, MIN_KIMG_ALIGN) +
87 kernel_memsize;
88
> 89 if (IS_ALIGNED((u64)_start, MIN_KIMG_ALIGN)) {
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 19000 bytes --]
next prev parent reply other threads:[~2020-04-16 1:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 19:54 [v3 PATCH 0/5] Add UEFI support for RISC-V Atish Patra
2020-04-15 19:54 ` [v3 PATCH 1/5] efi: Move arm-stub to a common file Atish Patra
2020-04-15 19:54 ` [v3 PATCH 2/5] include: pe.h: Add RISC-V related PE definition Atish Patra
2020-04-15 19:54 ` [v3 PATCH 3/5] RISC-V: Define fixmap bindings for generic early ioremap support Atish Patra
2020-04-15 19:54 ` [v3 PATCH 4/5] RISC-V: Add PE/COFF header for EFI stub Atish Patra
2020-04-15 19:54 ` [v3 PATCH 5/5] RISC-V: Add EFI stub support Atish Patra
2020-04-16 1:13 ` kbuild test robot [this message]
2020-04-16 7:41 ` Ard Biesheuvel
2020-04-18 3:03 ` Atish Patra
2020-04-18 10:51 ` Ard Biesheuvel
2020-04-18 12:39 ` Ard Biesheuvel
2020-04-18 19:19 ` Atish Patra
2020-04-18 19:24 ` Ard Biesheuvel
2020-04-20 4:20 ` Atish Patra
2020-04-20 7:03 ` Ard Biesheuvel
2020-04-20 7:59 ` Atish Patra
2020-04-20 8:02 ` Ard Biesheuvel
2020-04-21 5:06 ` Atish Patra
2020-04-16 7:44 ` [v3 PATCH 0/5] Add UEFI support for RISC-V Ard Biesheuvel
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=202004160922.dSCn2sEV%lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
/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