From: Jakub Kicinski <kuba@kernel.org>
To: Eyal Birger <eyal.birger@gmail.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2] remove support for iptables action
Date: Thu, 4 Jan 2024 07:25:52 -0800 [thread overview]
Message-ID: <20240104072552.1de9338f@kernel.org> (raw)
In-Reply-To: <CAM0EoMmH-5Afhe1DvhSJzMhsyx=y7AW+FnhR8p3YbveP3UigXA@mail.gmail.com>
On Wed, 27 Dec 2023 12:25:24 -0500 Jamal Hadi Salim wrote:
> On Tue, Dec 26, 2023 at 1:25 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > There is an open upstream kernel patch to remove ipt action from
> > kernel. This is corresponding iproute2 change.
> >
> > - Remove support fot ipt and xt in tc.
> > - Remove no longer used header files.
> > - Update man pages.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Does em_ipt need the m_xt*.c? Florian/Eyal can comment. Otherwise,
> Reviewed-by: Jamal Hadi Salim <jhs@mojatatu.com>
Damn, I was waiting for Eyal to comment but you didn't CC
either him or Florian 😆️
Eyal, would it be possible for you to test if the latest
net-next and iproute2 with this patch works for you?
next prev parent reply other threads:[~2024-01-04 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 18:25 [PATCH iproute2-next v2] remove support for iptables action Stephen Hemminger
2023-12-27 17:25 ` Jamal Hadi Salim
2024-01-04 15:25 ` Jakub Kicinski [this message]
2024-01-04 16:15 ` Jamal Hadi Salim
2024-01-05 2:33 ` Eyal Birger
2024-01-05 11:20 ` Jamal Hadi Salim
2024-01-05 14:09 ` Jakub Kicinski
2024-01-06 4:15 ` Eyal Birger
2024-01-08 1:50 ` patchwork-bot+netdevbpf
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=20240104072552.1de9338f@kernel.org \
--to=kuba@kernel.org \
--cc=eyal.birger@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 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.