All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ebtables: fix arm64 build with kernel headers >= 7.3
Date: Sun, 25 Oct 2026 21:53:16 +0100	[thread overview]
Message-ID: <at5sKfzIK4Xu8D8r@windsurf> (raw)
In-Reply-To: <20261024220900.1594745-1-yegorslists@googlemail.com>

On Sun, Oct 25, 2026 at 12:09:00AM +0200, Yegor Yefremov via buildroot wrote:
> Hi Thomas,
> 
> On Sat, Oct 24, 2026 at 11:16:38PM +0200, Thomas Petazzoni wrote:
> > And is the "opposite" still working, i.e building with really old
> > kernel headers? Maybe they lack something that the bundled copy had,
> > and it was the reason for this bundled copy in the first place?
> 
> Yes, it still builds. I tested ebtables with this patch against the
> oldest kernel headers Buildroot can use:
> 
> - x86_64, uClibc-ng, kernel headers 3.0.101
> - x86_64, glibc, kernel headers 3.2.102 (the minimum for glibc)
> 
> Both build fine without the bundled linux/types.h.

Thanks a lot for the additional thorough testing, and quick feedback!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-25 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 16:17 [Buildroot] [PATCH] package/ebtables: fix arm64 build with kernel headers >= 7.3 Yegor Yefremov via buildroot
2026-10-24 21:16 ` Thomas Petazzoni via buildroot
2026-10-24 22:09   ` Yegor Yefremov via buildroot
2026-10-25 20:53     ` Thomas Petazzoni via buildroot [this message]
2026-10-25 20:52 ` Thomas Petazzoni via buildroot

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=at5sKfzIK4Xu8D8r@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yegorslists@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.