From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, xiyou.wangcong@gmail.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
stephen@networkplumber.org, dsahern@gmail.com
Subject: Re: [PATCH net-next 0/5] net/sched: Retire some tc qdiscs and classifiers
Date: Tue, 14 Feb 2023 16:41:13 -0800 [thread overview]
Message-ID: <20230214164113.0c25dfdd@kernel.org> (raw)
In-Reply-To: <CAM0EoMmcMWrLueyaEco6r+VDbgLDmLf7O=80a8Rd+AJo-ScQOQ@mail.gmail.com>
On Tue, 14 Feb 2023 18:52:18 -0500 Jamal Hadi Salim wrote:
> So it will work in either case (of deleting or keeping the uapi
> around). It may be a bad sample space - but if we do keep the uapi,
> how long would that be for?
Last time we deleted some ATM driver and the uAPI removal broke
a random ATN package in debian, IIRC. The due diligence would probably
mean trying to find out if there's anything in debian which needs those
defines..
Is it possible to "download all the debian sources"? Or those which
depend on the kernel headers?
next prev parent reply other threads:[~2023-02-15 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 13:49 [PATCH net-next 0/5] net/sched: Retire some tc qdiscs and classifiers Jamal Hadi Salim
2023-02-14 13:49 ` [PATCH net-next 1/5] net/sched: Retire CBQ qdisc Jamal Hadi Salim
2023-02-14 13:49 ` [PATCH net-next 2/5] net/sched: Retire ATM qdisc Jamal Hadi Salim
2023-02-14 13:49 ` [PATCH net-next 3/5] net/sched: Retire dsmark qdisc Jamal Hadi Salim
2023-02-14 13:49 ` [PATCH net-next 4/5] net/sched: Retire tcindex classifier Jamal Hadi Salim
2023-02-14 13:49 ` [PATCH net-next 5/5] net/sched: Retire rsvp classifier Jamal Hadi Salim
2023-02-14 14:01 ` iproute2/user space code obsoletion when depending on kernel features WAS([PATCH net-next 0/5] net/sched: Retire some tc qdiscs and classifiers) Jamal Hadi Salim
2023-02-14 14:25 ` [PATCH net-next 0/5] net/sched: Retire some tc qdiscs and classifiers Jiri Pirko
2023-02-14 21:40 ` Jakub Kicinski
2023-02-14 21:41 ` Jakub Kicinski
2023-02-14 23:05 ` Jamal Hadi Salim
2023-02-14 23:22 ` Jakub Kicinski
2023-02-14 23:52 ` Jamal Hadi Salim
2023-02-15 0:41 ` Jakub Kicinski [this message]
2023-02-15 7:50 ` Jiri Pirko
2023-02-15 13:42 ` Pedro Tammela
2023-02-15 16:37 ` Jamal Hadi Salim
2023-02-16 8:51 ` Paolo Abeni
2023-02-16 9:00 ` 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=20230214164113.0c25dfdd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--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).