From: patchwork-bot+linux-riscv@kernel.org
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-riscv@lists.infradead.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, ardb@kernel.org,
torvalds@linux-foundation.org, masahiroy@kernel.org,
linux-s390@vger.kernel.org, re@w6rz.net
Subject: Re: [PATCH v3] kbuild: Strip runtime const RELA sections correctly
Date: Mon, 03 Feb 2025 19:16:08 +0000 [thread overview]
Message-ID: <173861016800.3409359.5303891262863199475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250113155306.1922992-2-ardb+git@google.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Masahiro Yamada <masahiroy@kernel.org>:
On Mon, 13 Jan 2025 16:53:07 +0100 you wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> Due to the fact that runtime const ELF sections are named without a
> leading period or double underscore, the RSTRIP logic that removes the
> static RELA sections from vmlinux fails to identify them. This results
> in a situation like below, where some sections that were supposed to get
> removed are left behind.
>
> [...]
Here is the summary with links:
- [v3] kbuild: Strip runtime const RELA sections correctly
https://git.kernel.org/riscv/c/71d815bf5dfd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 15:53 [PATCH v3] kbuild: Strip runtime const RELA sections correctly Ard Biesheuvel
2025-01-16 22:02 ` Charlie Jenkins
2025-01-19 17:15 ` Ard Biesheuvel
2025-01-22 16:49 ` Alexander Gordeev
2025-01-22 17:22 ` Alexander Gordeev
2025-01-31 18:35 ` Masahiro Yamada
2025-01-31 18:40 ` Ard Biesheuvel
2025-01-31 18:57 ` Masahiro Yamada
2025-01-31 19:02 ` Ard Biesheuvel
2025-01-31 19:27 ` Masahiro Yamada
2025-02-03 19:16 ` 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=173861016800.3409359.5303891262863199475.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=re@w6rz.net \
--cc=torvalds@linux-foundation.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