From: Cong Wang <xiyou.wangcong@gmail.com>
To: Victor Nogueira <victor@mojatatu.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Lion Ackermann <nnamrec@gmail.com>,
netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>,
Mingi Cho <mincho@theori.io>
Subject: Re: Incomplete fix for recent bug in tc / hfsc
Date: Mon, 30 Jun 2025 14:42:10 -0700 [thread overview]
Message-ID: <aGMEsnYnv0lwBTcl@pop-os.localdomain> (raw)
In-Reply-To: <442716ca-ae2e-4fac-8a01-ced3562fd588@mojatatu.com>
On Mon, Jun 30, 2025 at 02:52:19PM -0300, Victor Nogueira wrote:
> Lion, I attached a patch to this email that edits Cong's original tdc test
> case to account for your reproducer. Please resend your patch with it (after
> the 24 hour wait period).
Or send it as a follow up patch? I am fine either way, since we don't
backport selftests, this is not a big deal.
Thanks for improving the selftest!
next prev parent reply other threads:[~2025-06-30 21:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 10:41 Incomplete fix for recent bug in tc / hfsc Lion Ackermann
2025-06-23 14:43 ` Jamal Hadi Salim
2025-06-24 4:41 ` Cong Wang
2025-06-24 9:24 ` Lion Ackermann
2025-06-24 10:43 ` Lion Ackermann
2025-06-25 14:22 ` Jamal Hadi Salim
2025-06-26 8:08 ` Lion Ackermann
2025-06-28 21:43 ` Jamal Hadi Salim
2025-06-29 14:29 ` Jamal Hadi Salim
2025-06-29 19:50 ` Cong Wang
2025-06-30 9:04 ` Lion Ackermann
2025-06-30 11:34 ` Jamal Hadi Salim
2025-06-30 13:36 ` Lion Ackermann
2025-06-30 14:57 ` Jamal Hadi Salim
2025-06-30 17:52 ` Victor Nogueira
2025-06-30 21:42 ` Cong Wang [this message]
2025-07-01 12:41 ` Lion Ackermann
2025-07-01 12:58 ` Victor Nogueira
2025-06-30 11:47 ` Victor Nogueira
2025-06-30 13:27 ` [PATCH] net/sched: Always pass notifications when child class becomes empty Lion Ackermann
2025-06-30 14:56 ` Jamal Hadi Salim
2025-06-30 21:38 ` Cong Wang
2025-07-01 14:03 ` Jamal Hadi Salim
2025-07-02 21:50 ` patchwork-bot+netdevbpf
2025-06-28 0:35 ` Incomplete fix for recent bug in tc / hfsc Cong Wang
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=aGMEsnYnv0lwBTcl@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=mincho@theori.io \
--cc=netdev@vger.kernel.org \
--cc=nnamrec@gmail.com \
--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