From: Nathan Chancellor <nathan@kernel.org>
To: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb+git@google.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>, Kees Cook <kees@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kbuild@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Simplify kallsyms offset table generation
Date: Thu, 29 Jan 2026 17:10:31 -0700 [thread overview]
Message-ID: <176973183159.175491.9742885221630963935.b4-ty@kernel.org> (raw)
In-Reply-To: <20260116093359.2442297-4-ardb+git@google.com>
On Fri, 16 Jan 2026 10:34:00 +0100, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> v2:
> - implement minimal PC32 support for MIPS so it can tolerate the symbol
> references emitted by kallsyms
> - use signed decimal to represent the offset, so that symbols appearing
> before _text can be represented correctly.
> - add Kees's ack
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next
Thanks!
[1/2] mips: Add support for PC32 relocations in vmlinux
(no commit info)
[2/2] kallsyms: Get rid of kallsyms relative base
(no commit info)
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
prev parent reply other threads:[~2026-01-30 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:34 Ard Biesheuvel
2026-01-16 9:34 ` [PATCH v2 1/2] mips: Add support for PC32 relocations in vmlinux Ard Biesheuvel
2026-01-16 9:34 ` [PATCH v2 2/2] kallsyms: Get rid of kallsyms relative base Ard Biesheuvel
2026-01-30 0:10 ` Nathan Chancellor [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=176973183159.175491.9742885221630963935.b4-ty@kernel.org \
--to=nathan@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nsc@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®