From: Thomas Monjalon <thomas@monjalon.net>
To: Junlong Wang <wang.junlong1@zte.com.cn>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1 1/3] net/zxdh: modify some MAC config issues
Date: Thu, 12 Jun 2025 02:14:11 +0200 [thread overview]
Message-ID: <11989263.ag9G3TJQzC@thomas> (raw)
In-Reply-To: <20250607023020.3051575-1-wang.junlong1@zte.com.cn>
Hello,
07/06/2025 04:30, Junlong Wang:
> modify some mac config issues,
> which were discovered during the testing process.
>
> Signed-off-by: Junlong Wang <wang.junlong1@zte.com.cn>
That's not how we fix issues in general in DPDK.
We want to provide tracking history, so:
- we split the fixes per issue
- we provide the cause origin (with "Fixes:" line)
Please could split and better comment these fixes?
Thanks
next prev parent reply other threads:[~2025-06-12 0:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 2:30 [PATCH v1 1/3] net/zxdh: modify some MAC config issues Junlong Wang
2025-06-07 2:30 ` [PATCH v1 2/3] net/zxdh: modify some VLAN related issues Junlong Wang
2025-06-16 16:20 ` Stephen Hemminger
2025-06-07 2:30 ` [PATCH v1 3/3] net/zxdh: modify RSS " Junlong Wang
2025-06-16 16:22 ` Stephen Hemminger
2025-06-12 0:14 ` Thomas Monjalon [this message]
2025-06-12 1:18 ` [PATCH v1 1/3] net/zxdh: modify some MAC config issues Junlong Wang
2025-06-16 16:16 ` Stephen Hemminger
2025-06-17 2:04 ` [PATCH v2 1/5] net/zxdh: fix meson.build issus in compilation Junlong Wang
2025-06-17 2:05 ` [PATCH v2 2/5] net/zxdh: modify some MAC config issues Junlong Wang
2025-06-17 2:05 ` [PATCH v2 3/5] net/zxdh: modify some VLAN related issues Junlong Wang
2025-06-17 2:05 ` [PATCH v2 4/5] net/zxdh: modify RSS " Junlong Wang
2025-06-17 2:05 ` [PATCH v2 5/5] net/zxdh: add support VLAN TPID set ops Junlong Wang
2025-06-17 3:32 ` zhoumin
2025-06-17 14:01 ` [PATCH v2 1/5] net/zxdh: fix meson.build issus in compilation Stephen Hemminger
2025-06-17 15:20 ` Stephen Hemminger
2025-06-18 1:41 ` [v2,1/5] " Junlong 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=11989263.ag9G3TJQzC@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=wang.junlong1@zte.com.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.