From: Nicolas Schier <nsc@kernel.org>
To: "Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>,
"Nathan Chancellor" <nathan@kernel.org>
Cc: "Christian Heusel" <christian@heusel.eu>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: pacman-pkg: package unstripped vDSO libraries
Date: Wed, 13 May 2026 17:37:07 +0200 [thread overview]
Message-ID: <agSao7trp7eYmSl3@levanger> (raw)
In-Reply-To: <4c443339-5aa2-442c-a581-df25cc288468@freenet.de>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Wed, May 13, 2026 at 12:34:57AM +0200, Viktor Jägersküpper wrote:
> Am 30.03.26 um 21:30 schrieb Nicolas Schier:
> > On Wed, 18 Mar 2026 21:37:20 +0100, Thomas Weißschuh wrote:
> >> The unstripped vDSO files are useful for debugging.
> >> They are provided in the upstream 'linux-headers' package.
> >>
> >> Also package them as part of 'make pacman-pkg'.
> >> Make them part of the '-debug' package, as they fit there best.
> >> This differs from the upstream package as that has no '-debug' variant.
> >>
> >> [...]
> >
> > Applied to kbuild/linux.git (kbuild-next-unstable), thanks!
> >
> > [1/1] kbuild: pacman-pkg: package unstripped vDSO libraries
> > https://git.kernel.org/kbuild/c/165e86c2
>
> I can't find this patch anywhere (mainline, linux-next, kbuild branches),
> but there are no further comments on the mailing lists.
>
> Was the patch dropped or did it get lost?
thanks for spotting! You're right, it got lost. I have that commit still in my
local git tree but w/o any branch referencing it. I'm sorry.
Nathan, can you please pick this one up for v7.2?
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-13 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 20:37 [PATCH] kbuild: pacman-pkg: package unstripped vDSO libraries Thomas Weißschuh
2026-03-19 22:30 ` Nathan Chancellor
2026-03-30 19:30 ` Nicolas Schier
2026-05-12 22:34 ` Viktor Jägersküpper
2026-05-13 15:37 ` Nicolas Schier [this message]
2026-05-14 12:47 ` Nathan Chancellor
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=agSao7trp7eYmSl3@levanger \
--to=nsc@kernel.org \
--cc=christian@heusel.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=nathan@kernel.org \
--cc=viktor_jaegerskuepper@freenet.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 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.