From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, toke@toke.dk, jiri@resnulli.us,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, cake@lists.bufferbloat.net,
victor@mojatatu.com, sashiko-bot@kernel.org
Subject: [Cake] Re: [PATCH net-next v3 0/4] net/sched: sch_cake: fixes for accounting and reconfiguration
Date: Thu, 22 Oct 2026 01:10:13 +0000 [thread overview]
Message-ID: <179263141302.1392288.3198241467821485238.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-5RTM.v3.r0.20261020053711@mojatatu.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Oct 2026 07:00:04 -0400 you wrote:
> Four independent fixes in the CAKE qdisc. Three are follow-ups to the
> autorate reconfiguration work around commit 7cbfb180945c ("net/sched:
> sch_cake: fix autorate reconfiguration throttling") and the 32-bit
> admission-counter wraps fixed in gred/bfifo/plug by commit 4c660ee8c809
> ("net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue");
> the fourth is a dead-code cleanup found while auditing the dump path.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] net/sched/sch_cake: serialize reconfiguration with the datapath
https://git.kernel.org/netdev/net-next/c/d23a16d907dc
- [net-next,v3,2/4] net/sched/sch_cake: reduce parent backlog when clearing a tin
https://git.kernel.org/netdev/net-next/c/d7010be1ba23
- [net-next,v3,3/4] net/sched/sch_cake: widen buffer_used to u64
https://git.kernel.org/netdev/net-next/c/dc48c97e7c69
- [net-next,v3,4/4] net/sched/sch_cake: drop dead nla_nest_end() error check
https://git.kernel.org/netdev/net-next/c/700b4c6c70d6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-22 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 11:00 [Cake] [PATCH net-next v3 0/4] net/sched: sch_cake: fixes for accounting and reconfiguration Jamal Hadi Salim
2026-10-20 11:00 ` [Cake] [PATCH net-next v3 1/4] net/sched/sch_cake: serialize reconfiguration with the datapath Jamal Hadi Salim
2026-10-20 11:00 ` [Cake] [PATCH net-next v3 2/4] net/sched/sch_cake: reduce parent backlog when clearing a tin Jamal Hadi Salim
2026-10-20 11:00 ` [Cake] [PATCH net-next v3 3/4] net/sched/sch_cake: widen buffer_used to u64 Jamal Hadi Salim
2026-10-20 11:00 ` [Cake] [PATCH net-next v3 4/4] net/sched/sch_cake: drop dead nla_nest_end() error check Jamal Hadi Salim
2026-10-20 12:55 ` [Cake] Re: [PATCH net-next v3 3/4] net/sched/sch_cake: widen buffer_used to u64 Toke Høiland-Jørgensen
2026-10-20 12:49 ` [Cake] Re: [PATCH net-next v3 1/4] net/sched/sch_cake: serialize reconfiguration with the datapath Toke Høiland-Jørgensen
2026-10-22 1:10 ` 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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179263141302.1392288.3198241467821485238.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cake@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=toke@toke.dk \
--cc=victor@mojatatu.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