[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-8cabcad9-a181-4db8-904b-3f7daa7621f1@palmer-ri-x1c9a>
Date: Wed, 20 Sep 2023 02:52:06 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: songshuaishuai@...ylab.org
CC: Paul Walmsley <paul.walmsley@...ive.com>, aou@...s.berkeley.edu,
anup@...infault.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, songshuaishuai@...ylab.org
Subject: Re: [PATCH -fixes] riscv: Remove duplicate objcopy flag
On Thu, 14 Sep 2023 02:13:34 PDT (-0700), songshuaishuai@...ylab.org wrote:
> There are two duplicate `-O binary` flags when objcopying from vmlinux
> to Image/xipImage.
>
> RISC-V set `-O binary` flag in both OBJCOPYFLAGS in the top-level riscv
> Makefile and OBJCOPYFLAGS_* in the boot/Makefile, and the objcopy cmd
> in Kbuild would join them together.
>
> The `-O binary` flag is only needed for objcopying Image, so remove the
> OBJCOPYFLAGS in the top-level riscv Makefile.
>
> Fixes: c0fbcd991860 ("RISC-V: Build flat and compressed kernel images")
> Signed-off-by: Song Shuai <songshuaishuai@...ylab.org>
> ---
> arch/riscv/Makefile | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/riscv/Makefile b/arch/riscv/Makefile
> index 1329e060c548..b43a6bb7e4dc 100644
> --- a/arch/riscv/Makefile
> +++ b/arch/riscv/Makefile
> @@ -6,7 +6,6 @@
> # for more details.
> #
>
> -OBJCOPYFLAGS := -O binary
> LDFLAGS_vmlinux := -z norelro
> ifeq ($(CONFIG_RELOCATABLE),y)
> LDFLAGS_vmlinux += -shared -Bsymbolic -z notext --emit-relocs
Does this result in any incorrect behavior? It looks fine to me, but if
there's no regression I'll put in on -next instead of -fixes.
Reviewed-by: Palmer Dabbelt <palmer@...osinc.com>
Powered by blists - more mailing lists