From: Thomas Monjalon <thomas@monjalon.net>
To: stephen@networkplumber.org,
Talluri Chaitanyababu <chaitanyababux.talluri@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>
Cc: stable@dpdk.org, dev@dpdk.org, bruce.richardson@intel.com,
aman.deep.singh@intel.com, shaiq.wani@intel.com
Subject: Re: [PATCH v3] app/testpmd: fix DCB forwarding TC mask and queue guard
Date: Tue, 17 Mar 2026 10:02:36 +0100 [thread overview]
Message-ID: <14422376.RDIVbhacDa@thomas> (raw)
In-Reply-To: <5157955.0VBMTVartN@thomas>
17/03/2026 09:57, Thomas Monjalon:
> 16/03/2026 07:21, Talluri Chaitanyababu:
> > Update forwarding TC mask based on configured traffic classes to properly
> > handle both 4 TC and 8 TC modes. The bitmask calculation (1u << nb_tcs) - 1
> > correctly creates masks for all available traffic classes (0xF for 4 TCs,
> > 0xFF for 8 TCs).
>
> I don't know why this patch was merged in next-net without any review.
> It has been pulled in main yesterday, sorry for that.
> You'll need to make another patch to fix after the complete review.
>
> Stephen, please don't merge too fast if no review.
After another thought, I've dropped it from main,
so you can continue with a v4 as usual.
next prev parent reply other threads:[~2026-03-17 9:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 8:37 [PATCH] app/testpmd: fix DCB forwarding TC mask and queue guard Talluri Chaitanyababu
2026-03-11 15:56 ` Stephen Hemminger
2026-03-12 10:36 ` [PATCH v2] " Talluri Chaitanyababu
2026-03-12 18:44 ` Stephen Hemminger
2026-03-13 0:19 ` fengchengwen
2026-03-16 6:05 ` Talluri, ChaitanyababuX
2026-03-17 1:07 ` fengchengwen
2026-03-18 7:21 ` Talluri, ChaitanyababuX
2026-03-19 1:19 ` fengchengwen
2026-03-16 6:21 ` [PATCH v3] " Talluri Chaitanyababu
2026-03-17 1:23 ` fengchengwen
2026-03-17 8:57 ` Thomas Monjalon
2026-03-17 9:02 ` Thomas Monjalon [this message]
2026-03-18 6:17 ` [PATCH v4] app/testpmd: fix DCB forwarding TC mismatch handling Talluri Chaitanyababu
2026-03-19 1:35 ` fengchengwen
2026-03-20 6:29 ` [PATCH v5] " Talluri Chaitanyababu
2026-03-20 9:38 ` fengchengwen
2026-03-24 0:06 ` Stephen Hemminger
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=14422376.RDIVbhacDa@thomas \
--to=thomas@monjalon.net \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chaitanyababux.talluri@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=shaiq.wani@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
/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