From: Thomas Monjalon <thomas@monjalon.net>
To: Liangxing Wang <wangliangxing@hygon.cn>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2 1/3] examples/l3fwd: extend NUMA nodes limit beyond 8
Date: Wed, 21 Jan 2026 10:40:06 +0100 [thread overview]
Message-ID: <15656361.tv2OnDr8pf@thomas> (raw)
In-Reply-To: <c0fde19abc9e4b44b2d21a9cf22553e8@hygon.cn>
19/01/2026 10:19, Liangxing Wang:
> Hi,
>
> Not sure for what reason, there wasn't any test check triggered by this patch. Do I have to submit a new patch version to trigger the tests? Thanks.
The whole series got tested and reported on the last patch:
https://patches.dpdk.org/project/dpdk/patch/20260108073135.1279814-1-wangliangxing@hygon.cn/
next prev parent reply other threads:[~2026-01-21 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 7:29 [PATCH v2 1/3] examples/l3fwd: extend NUMA nodes limit beyond 8 Liangxing Wang
2026-01-19 9:19 ` Liangxing Wang
2026-01-21 9:40 ` Thomas Monjalon [this message]
2026-01-21 10:50 ` Liangxing Wang
2026-02-10 10:15 ` Liangxing Wang
2026-02-10 13:30 ` Thomas Monjalon
2026-02-12 10:44 ` Liangxing 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=15656361.tv2OnDr8pf@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=stephen@networkplumber.org \
--cc=wangliangxing@hygon.cn \
/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