From: Jakub Kicinski <kuba@kernel.org>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: Simon Horman <horms@kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
netdev@vger.kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
mincho@theori.io, quanglex97@gmail.com,
Cong Wang <cong.wang@bytedance.com>
Subject: Re: [Patch net v3 2/4] selftests/tc-testing: Add a test case for pfifo_head_drop qdisc when limit==0
Date: Tue, 4 Feb 2025 18:38:51 -0800 [thread overview]
Message-ID: <20250204183851.55ec662e@kernel.org> (raw)
In-Reply-To: <b06cc0bb-167d-4cac-b5df-83884b274613@mojatatu.com>
On Tue, 4 Feb 2025 23:21:07 -0300 Pedro Tammela wrote:
> > This is starting to feel too much like a setup issue.
> > Pedro, would you be able to take this series and investigate
> > why it fails on the TDC runner?
>
> It should be OK now
Thank you!
Revived in PW, should get into the run 22 min from now.
next prev parent reply other threads:[~2025-02-05 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 0:58 [Patch net v3 0/4] net_sched: two security bug fixes and test cases Cong Wang
2025-02-04 0:58 ` [Patch net v3 1/4] pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Cong Wang
2025-02-04 11:32 ` Simon Horman
2025-02-06 17:40 ` Cong Wang
2025-02-04 0:58 ` [Patch net v3 2/4] selftests/tc-testing: Add a test case for pfifo_head_drop qdisc when limit==0 Cong Wang
2025-02-04 11:37 ` Simon Horman
2025-02-04 16:46 ` Jakub Kicinski
2025-02-05 2:21 ` Pedro Tammela
2025-02-05 2:38 ` Jakub Kicinski [this message]
2025-02-05 17:20 ` Simon Horman
2025-02-06 17:37 ` Cong Wang
2025-02-04 0:58 ` [Patch net v3 3/4] netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() Cong Wang
2025-02-04 0:58 ` [Patch net v3 4/4] selftests/tc-testing: Add a test case for qdisc_tree_reduce_backlog() Cong Wang
2025-02-06 2:20 ` [Patch net v3 0/4] net_sched: two security bug fixes and test cases 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=20250204183851.55ec662e@kernel.org \
--to=kuba@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=mincho@theori.io \
--cc=netdev@vger.kernel.org \
--cc=pctammela@mojatatu.com \
--cc=quanglex97@gmail.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).