Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, jiri@resnulli.us, xiyou.wangcong@gmail.com,
	netdev@vger.kernel.org, stephen@networkplumber.org,
	dsahern@gmail.com, pctammela@mojatatu.com, victor@mojatatu.com
Subject: Re: [PATCH net-next 0/5] net/sched: Remove UAPI support for retired TC qdiscs and classifiers
Date: Tue, 02 Jan 2024 14:30:29 +0000	[thread overview]
Message-ID: <170420582982.19051.4039294495486636536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231223140154.1319084-1-jhs@mojatatu.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Sat, 23 Dec 2023 09:01:49 -0500 you wrote:
> Classifiers RSVP and tcindex as well as qdiscs dsmark, CBQ and ATM have already
> been deleted. This patchset removes their UAPI support.
> 
> User space - with a focus on iproute2 - typically copies these UAPI headers for
> different kernels.
> These deletion patches are coordinated with the iproute2 maintainers to make
> sure that they delete any user space code referencing removed objects at their
> leisure.
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] net/sched: Remove uapi support for rsvp classifier
    https://git.kernel.org/netdev/net-next/c/41bc3e8fc1f7
  - [net-next,2/5] net/sched: Remove uapi support for tcindex classifier
    https://git.kernel.org/netdev/net-next/c/82b2545ed9a4
  - [net-next,3/5] net/sched: Remove uapi support for dsmark qdisc
    https://git.kernel.org/netdev/net-next/c/fe3b739a5472
  - [net-next,4/5] net/sched: Remove uapi support for ATM qdisc
    https://git.kernel.org/netdev/net-next/c/26cc8714fc7f
  - [net-next,5/5] net/sched: Remove uapi support for CBQ qdisc
    https://git.kernel.org/netdev/net-next/c/33241dca4862

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-02 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 14:01 [PATCH net-next 0/5] net/sched: Remove UAPI support for retired TC qdiscs and classifiers Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 1/5] net/sched: Remove uapi support for rsvp classifier Jamal Hadi Salim
2023-12-23 17:16   ` Stephen Hemminger
2023-12-23 21:15     ` Jamal Hadi Salim
2024-01-01 18:56     ` Cong Wang
2023-12-23 14:01 ` [PATCH net-next 2/5] net/sched: Remove uapi support for tcindex classifier Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 3/5] net/sched: Remove uapi support for dsmark qdisc Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 4/5] net/sched: Remove uapi support for ATM qdisc Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 5/5] net/sched: Remove uapi support for CBQ qdisc Jamal Hadi Salim
2024-01-01 18:58 ` [PATCH net-next 0/5] net/sched: Remove UAPI support for retired TC qdiscs and classifiers Cong Wang
2024-01-02 14:30 ` patchwork-bot+netdevbpf [this message]

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=170420582982.19051.4039294495486636536.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --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