Re: [PATCH v2 0/2] riscv: make image compression configurable - patchwork-bot+linux-riscv

From: patchwork-bot+linux-riscv@kernel.org
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-kbuild@vger.kernel.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, masahiroy@kernel.org, nathan@kernel.org,
	nicolas@fjasle.eu, terrelln@fb.com
Subject: Re: [PATCH v2 0/2] riscv: make image compression configurable
Date: Wed, 15 May 2024 13:40:35 +0000	[thread overview]
Message-ID: <171578043522.14005.5445713768197740936.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240504193446.196886-1-emil.renner.berthing@canonical.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Sat,  4 May 2024 21:34:37 +0200 you wrote:
> Masahiro's patch[1] made me wonder why we're not just using KBUILD_IMAGE
> to determine which (possibly compressed) kernel image to use in 'make
> tar-pkg' like other architectures do. It turns out we're always setting
> KBUILD_IMAGE to the uncompressed Image file and then compressing it into
> the Image.gz file afterwards.
> 
> This series fixes that so the compression method is configurable and
> KBUILD_IMAGE is set to the chosen (possibly uncompressed) kernel image
> which is then used by targets like 'make install' and 'make bindeb-pkg' and
> 'make tar-pkg'.
> 
> [...]

Here is the summary with links:
  - [v2,1/2] riscv: make image compression configurable
    https://git.kernel.org/riscv/c/c1f59d035966
  - [v2,2/2] riscv: show help string for riscv-specific targets
    https://git.kernel.org/riscv/c/5e3964ba8400

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html