From: Sam James <sam@gentoo.org>
To: linux@weissschuh.net
Cc: bp@alien8.de,dave.hansen@linux.intel.com,hpa@zytor.com,linux-kernel@vger.kernel.org,mingo@redhat.com,stable@vger.kernel.org,tglx@kernel.org,theron.york@cloudnuke.org,x86@kernel.org
Subject: Re: [PATCH] x86/tools: Only use unprocessed UAPI headers for vdso2c
Date: Wed, 19 Aug 2026 01:31:08 +0100 [thread overview]
Message-ID: <878q632boz.fsf@gentoo.org> (raw)
In-Reply-To: <20260530-x86-tools-build-fix2-v1-1-2eb92ed1b0b7@weissschuh.net>
[-- Attachment #1: Type: text/plain, Size: 40 bytes --]
Gentle ping. It works for us in Gentoo.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 418 bytes --]
prev parent reply other threads:[~2026-08-19 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 10:23 [PATCH] x86/tools: Only use unprocessed UAPI headers for vdso2c Thomas Weißschuh
2026-08-19 0:31 ` Sam James [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=878q632boz.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=theron.york@cloudnuke.org \
--cc=x86@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