From: "Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>
To: "Nicolas Schier" <nsc@kernel.org>,
"Christian Heusel" <christian@heusel.eu>,
"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] kbuild: pacman-pkg: package unstripped vDSO libraries
Date: Wed, 13 May 2026 00:34:57 +0200 [thread overview]
Message-ID: <4c443339-5aa2-442c-a581-df25cc288468@freenet.de> (raw)
In-Reply-To: <177489899701.2334687.2954985636789986091.b4-ty@b4>
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?
Best regards,
Viktor
next prev parent reply other threads:[~2026-05-12 22:40 UTC|newest]
Thread overview: 5+ 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 [this message]
2026-05-13 15:37 ` Nicolas Schier
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=4c443339-5aa2-442c-a581-df25cc288468@freenet.de \
--to=viktor_jaegerskuepper@freenet.de \
--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=nsc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox