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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-05-15 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 19:34 [PATCH v2 0/2] riscv: make image compression configurable Emil Renner Berthing
2024-05-04 19:34 ` [PATCH v2 1/2] " Emil Renner Berthing
2024-05-07 12:34 ` Nicolas Schier
2024-05-07 14:26 ` Masahiro Yamada
2024-05-04 19:34 ` [PATCH v2 2/2] riscv: show help string for riscv-specific targets Emil Renner Berthing
2024-05-07 14:26 ` Masahiro Yamada
2024-05-15 13:40 ` patchwork-bot+linux-riscv [this message]
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=171578043522.14005.5445713768197740936.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=terrelln@fb.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).