All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Alyssa Ross <hi@alyssa.is>,
	netfilter-devel@vger.kernel.org,
	Joshua Lant <joshualant@googlemail.com>
Subject: Re: [PATCH nftables] include: fix for musl with iptables v1.8.11
Date: Wed, 11 Feb 2026 20:09:30 +0100	[thread overview]
Message-ID: <aYzT6kHV7ntq5kfo@strlen.de> (raw)
In-Reply-To: <aYzRlXaSetejciwU@orbyte.nwl.cc>

Phil Sutter <phil@nwl.cc> wrote:
> > Phil, would you send a formal patch to make this workaround *ONLY* in
> > netfilter_bridge.h (06e445f740c1)?
> 
> DONE.

Thanks.

> > That way the fix can be propagated to nftables.git without having to
> > adjust cached headers on every update.
> 
> I assume you prefer to keep headers untouched which are
> iptables-specific. But why not attempt to patch if_ether.h itself?

Because this is a quagmire and I prefer to only break netfiler_bridge.h
users (which should be few) rather than everyone using if_ether.h.

  reply	other threads:[~2026-02-11 19:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 23:10 [PATCH nftables] include: fix for musl with iptables v1.8.11 Alyssa Ross
2024-12-20 11:50 ` Phil Sutter
2024-12-20 12:07   ` Alyssa Ross
2024-12-20 12:33     ` Phil Sutter
2024-12-21 15:34       ` Alyssa Ross
2025-01-08 23:34       ` Pablo Neira Ayuso
2025-01-08 23:49         ` Phil Sutter
2025-01-09  0:03           ` Pablo Neira Ayuso
2025-01-09 10:02             ` Phil Sutter
2026-02-11 13:49               ` Florian Westphal
2026-02-11 18:59                 ` Phil Sutter
2026-02-11 19:09                   ` Florian Westphal [this message]
2026-02-11 20:19                     ` Phil Sutter

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=aYzT6kHV7ntq5kfo@strlen.de \
    --to=fw@strlen.de \
    --cc=hi@alyssa.is \
    --cc=joshualant@googlemail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    /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.