From: Stephen Hemminger <stephen@networkplumber.org>
To: Wencheng Li <liwencheng@phytium.com.cn>
Cc: dev@dpdk.org
Subject: Re: [PATCH v10 3/3] net/macb: add necessary docs and update related files
Date: Wed, 20 Aug 2025 08:12:41 -0700 [thread overview]
Message-ID: <20250820081241.43462fbd@hermes.local> (raw)
In-Reply-To: <1755664500-9517-1-git-send-email-liwencheng@phytium.com.cn>
On Wed, 20 Aug 2025 04:35:00 +0000
Wencheng Li <liwencheng@phytium.com.cn> wrote:
> diff --git a/doc/guides/rel_notes/release_25_11.rst b/doc/guides/rel_notes/release_25_11.rst
> index ccad6d8..8a66081 100644
> --- a/doc/guides/rel_notes/release_25_11.rst
> +++ b/doc/guides/rel_notes/release_25_11.rst
> @@ -24,36 +24,10 @@ DPDK Release 25.11
> New Features
> ------------
>
> -.. This section should contain new features added in this release.
> - Sample format:
> +* **Added Phytium macb net driver.**
>
> - * **Add a title in the past tense with a full stop.**
> -
> - Add a short 1-2 sentence description in the past tense.
> - The description should be enough to allow someone scanning
> - the release notes to understand the new feature.
> -
> - If the feature adds a lot of sub-features you can use a bullet list
> - like this:
> -
> - * Added feature foo to do something.
> - * Enhanced feature bar to do something else.
> -
> - Refer to the previous release notes for examples.
> -
> - Suggested order in release notes items:
> - * Core libs (EAL, mempool, ring, mbuf, buses)
> - * Device abstraction libs and PMDs (ordered alphabetically by vendor name)
> - - ethdev (lib, PMDs)
> - - cryptodev (lib, PMDs)
> - - eventdev (lib, PMDs)
> - - etc
> - * Other libs
> - * Apps, Examples, Tools (if significant)
> -
> - This section is a comment. Do not overwrite or remove it.
> - Also, make sure to start the actual text at the margin.
> - =======================================================
> + Added a new network PMD which supports Phytium 1 and 10 Gigabit
> + Ethernet NICs.
>
Please leave the template text there, it is only removed just before release.
Just add your entry after the template.
prev parent reply other threads:[~2025-08-20 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 7:10 [PATCH v3 6/6] " Wencheng Li
2025-04-02 7:11 ` [PATCH v4 4/4] " liwencheng
2025-04-07 6:40 ` [PATCH v5 " liwencheng
2025-04-07 18:23 ` Stephen Hemminger
2025-04-08 6:22 ` [PATCH v6 3/3] " liwencheng
2025-04-18 3:27 ` [PATCH v7 " Wencheng Li
2025-06-04 7:01 ` [PATCH v8 " Wencheng Li
2025-06-06 9:07 ` [PATCH v9 " Wencheng Li
2025-08-20 4:35 ` [PATCH v10 " Wencheng Li
2025-08-20 15:12 ` Stephen Hemminger [this message]
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=20250820081241.43462fbd@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=liwencheng@phytium.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 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).