From: Sasha Levin <sashal@kernel.org>
To: Marco Schirrmeister <mschirrmeister@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Will Deacon <will@kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>
Subject: Re: [6.18.y] Request: 10a47fb67340 ("tools: linux/types.h: Add 128-bit integer types for arm64 UAPI structures")
Date: Sat, 14 Nov 2026 12:42:15 -0500 [thread overview]
Message-ID: <draft-agent5-0004-re-tools-u128-typedef@kernel.org> (raw)
In-Reply-To: <avcSVAn5Q724e-yp@eagle.home.marco.cx>
On 2026-11-13, Marco Schirrmeister <mschirrmeister@gmail.com> wrote:
> With
> 10a47fb67340 applied, 6.18.63 builds again without issues.
Thanks, that answers it. Queued for 6.18, 6.12, 6.6, 6.1, 5.15 and 5.10.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-14 17:42 UTC|newest]
Thread overview: 4+ 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
2026-11-13 13:39 ` Marco Schirrmeister
2026-11-14 17:42 ` 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=draft-agent5-0004-re-tools-u128-typedef@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