From: David Ahern <dsahern@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
xiyou.wangcong@gmail.com, stephen@networkplumber.org,
fw@strlen.de, pctammela@mojatatu.com, victor@mojatatu.com
Subject: Re: [PATCH net-next 0/2] net/sched: retire tc ipt action
Date: Thu, 21 Dec 2023 20:51:10 -0700 [thread overview]
Message-ID: <6f24a4f8-fb07-409b-955a-9aad4ab37ca5@gmail.com> (raw)
In-Reply-To: <20231221213105.476630-1-jhs@mojatatu.com>
On 12/21/23 2:31 PM, Jamal Hadi Salim wrote:
> In keeping up with my status as a hero who removes code: another one bites the
> dust.
> The tc ipt action was intended to run all netfilter/iptables target.
> Unfortunately it has not benefitted over the years from proper updates when
> netfilter changes, and for that reason it has remained rudimentary.
> Pinging a bunch of people that i was aware were using this indicates that
> removing it wont affect them.
> Retire it to reduce maintenance efforts.
> So Long, ipt, and Thanks for all the Fish.
>
> Jamal Hadi Salim (2):
> net/sched: Retire ipt action
> net/sched: Remove CONFIG_NET_ACT_IPT from default configs
>
Acked-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-12-22 3:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 21:31 [PATCH net-next 0/2] net/sched: retire tc ipt action Jamal Hadi Salim
2023-12-21 21:31 ` [PATCH net-next 1/2] net/sched: Retire " Jamal Hadi Salim
2023-12-21 21:38 ` Pedro Tammela
2023-12-22 1:19 ` Stephen Hemminger
2023-12-22 2:02 ` David Ahern
2023-12-22 3:52 ` Stephen Hemminger
2023-12-22 10:45 ` Jamal Hadi Salim
2023-12-21 21:31 ` [PATCH net-next 2/2] net/sched: Remove CONFIG_NET_ACT_IPT from default configs Jamal Hadi Salim
2023-12-21 21:33 ` [PATCH net-next 0/2] net/sched: retire tc ipt action Florian Westphal
2023-12-22 3:51 ` David Ahern [this message]
2024-01-02 12: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=6f24a4f8-fb07-409b-955a-9aad4ab37ca5@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=stephen@networkplumber.org \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).