From: Nicolas Schier <nsc@kernel.org>
To: "Nathan Chancellor" <nathan@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] kbuild: vdso_install: drop build ID architecture allow-list
Date: Tue, 31 Mar 2026 19:09:46 +0200 [thread overview]
Message-ID: <acv_2nZNmPPal05p@levanger> (raw)
In-Reply-To: <177497336368.2732896.13736355342879030780.b4-ty@b4>
On Tue, Mar 31, 2026 at 06:09:39PM +0200, Nicolas Schier wrote:
> On Fri, 20 Mar 2026 17:36:52 +0100, Thomas Weißschuh wrote:
> > This list is incomplete. Instead of maintaining it manually,
> > detect a vDSO with build ID automatically and handle it.
>
> Applied to kbuild/linux.git (kbuild-next-unstable), thanks!
>
> [1/4] kbuild: vdso_install: split out the readelf invocation
> https://git.kernel.org/kbuild/c/9780cef0
> [2/4] kbuild: vdso_install: hide readelf warnings
> https://git.kernel.org/kbuild/c/6ba86c59
> [3/4] kbuild: vdso_install: gracefully handle images without build ID
> https://git.kernel.org/kbuild/c/5cd6177e
> [4/4] kbuild: vdso_install: drop build ID architecture allow-list
> https://git.kernel.org/kbuild/c/80b1f3e6
>
> Please look out for regression or issue reports or other follow up
> comments, as they may result in the patch/series getting dropped,
> reverted or modified (e.g. trailers). Patches applied to the
> kbuild-next-unstable branch are accepted pending wider testing in
> linux-next and any post-commit review; they will generally be moved
> to the kbuild-next branch in about a week if no issues are found.
>
> Best regards,
> --
> Nicolas
>
I didn't want to merge that already; please ignore. Sorry for the
noise.
--
Nicolas
prev parent reply other threads:[~2026-03-31 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 16:36 [PATCH 0/4] kbuild: vdso_install: drop build ID architecture allow-list Thomas Weißschuh
2026-03-20 16:36 ` [PATCH 1/4] kbuild: vdso_install: split out the readelf invocation Thomas Weißschuh
2026-03-31 15:15 ` Nicolas Schier
2026-03-20 16:36 ` [PATCH 2/4] kbuild: vdso_install: hide readelf warnings Thomas Weißschuh
2026-03-31 15:15 ` Nicolas Schier
2026-03-20 16:36 ` [PATCH 3/4] kbuild: vdso_install: gracefully handle images without build ID Thomas Weißschuh
2026-03-31 15:15 ` Nicolas Schier
2026-03-20 16:36 ` [PATCH 4/4] kbuild: vdso_install: drop build ID architecture allow-list Thomas Weißschuh
2026-03-31 15:15 ` Nicolas Schier
2026-03-31 16:09 ` [PATCH 0/4] " Nicolas Schier
2026-03-31 17:09 ` Nicolas Schier [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=acv_2nZNmPPal05p@levanger \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=nathan@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.