Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Will Deacon <will@kernel.org>,
	Jeremy Linton <jeremy.linton@arm.com>,
	Marco Schirrmeister <mschirrmeister@gmail.com>
Subject: Re: [6.18.y] Request: 10a47fb67340 ("tools: linux/types.h: Add 128-bit integer types for arm64 UAPI structures")
Date: Thu, 12 Nov 2026 21:33:22 -0500	[thread overview]
Message-ID: <daily-reply-2026-11-12-4571868778@kernel.org> (raw)
In-Reply-To: <avT46huKpXTv09GB@eagle.home.marco.cx>

On 2026-11-12, Marco Schirrmeister wrote:
> [6.18.y] Request: 10a47fb67340 ("tools: linux/types.h: Add 128-bit integer types for arm64 UAPI structures")
> Hi,
> please backport upstream commit
>   10a47fb67340 ("tools: linux/types.h: Add 128-bit integer types for arm64 UAPI structures")

10a47fb67340 ("tools: linux/types.h: Add 128-bit integer types for arm64 UAPI
structures") only adds typedefs for d4bf9e08d412 ("arm64: uapi: Use __u128
instead of __uint128_t in UAPI headers"), which no stable tree has, and nothing
in them uses the new types.

What breaks on 6.18.y without it? If it is the resolve_btfids build against
distro uapi headers, please say so and we can look again.


-- 
Thanks,
Sasha

      reply	other threads:[~2026-11-13  2:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 23:24 [6.18.y] Request: 10a47fb67340 ("tools: linux/types.h: Add 128-bit integer types for arm64 UAPI structures") Marco Schirrmeister
2026-11-13  2:33 ` Sasha Levin [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=daily-reply-2026-11-12-4571868778@kernel.org \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.linton@arm.com \
    --cc=mschirrmeister@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=will@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