From: Florian Westphal <fw@strlen.de>
To: Sebastien Bacher <sebastien.bacher@canonical.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ebtables PATCH] include: drop bundled copy of linux/types.h
Date: Wed, 7 Oct 2026 15:23:13 +0200 [thread overview]
Message-ID: <asZHwYyb0rlYXlYC@strlen.de> (raw)
In-Reply-To: <CAD04=wrZafKknWixGGRZWtYD_ydfdL4Uk39s_RkwZ6WUEVATKg@mail.gmail.com>
Sebastien Bacher <sebastien.bacher@canonical.com> wrote:
> The bundled include/linux/types.h is a copy of the kernel UAPI header
> from v3.16. Since the build uses -I./include, it shadows the system
> <linux/types.h>.
>
> Recent kernel UAPI headers (v7.3) changed arm64's asm/sigcontext.h,
> included via <signal.h>, to use the __u128 type from linux/types.h:
>
> - __uint128_t vregs[32];
> + __u128 vregs[32];
>
> The stale copy lacks __u128, so the build fails on arm64:
>
> /usr/include/aarch64-linux-gnu/asm/sigcontext.h:81:9: error: unknown
> type name '__u128'; did you mean '__u32'?
>
> The system header provides everything the bundled copy did, so drop it.
Applied, thanks.
prev parent reply other threads:[~2026-10-07 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 11:25 [ebtables PATCH] include: drop bundled copy of linux/types.h Sebastien Bacher
2026-10-07 13:23 ` Florian Westphal [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=asZHwYyb0rlYXlYC@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=sebastien.bacher@canonical.com \
/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