DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Feifei Wang <wff_light@vip.163.com>
Cc: dev@dpdk.org, Feifei Wang <wangfeifei40@huawei.com>,
	Yi Chen <chenyi221@huawei.com>,
	Xin Wang <wangxin679@h-partners.com>
Subject: Re: [RFC 01/18] net/hinic3: add intro doc for hinic3
Date: Tue, 20 May 2025 08:30:27 -0700	[thread overview]
Message-ID: <20250520083027.45f5077c@hermes.local> (raw)
In-Reply-To: <20250418070306.9290-2-wff_light@vip.163.com>

On Fri, 18 Apr 2025 15:02:39 +0800
Feifei Wang <wff_light@vip.163.com> wrote:

> diff --git a/doc/guides/rel_notes/release_25_07.rst b/doc/guides/rel_notes/release_25_07.rst
> index 093b85d206..1d65cf7829 100644
> --- a/doc/guides/rel_notes/release_25_07.rst
> +++ b/doc/guides/rel_notes/release_25_07.rst
> @@ -24,37 +24,9 @@ DPDK Release 25.07
>  New Features
>  ------------
>  
> -.. This section should contain new features added in this release.
> -   Sample format:
> -
> -   * **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 Huawei hinic3 net driver [EXPERIMENTAL].**
>  
> +  * Added network driver for the Huawei SPx series Network Adapters.

Leave the comment section in the release notes alone, it gets handled
as part of the release process.

  reply	other threads:[~2025-05-20 15:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  7:02 [RFC 00/18] add hinic3 PMD driver Feifei Wang
2025-04-18  7:02 ` [RFC 01/18] net/hinic3: add intro doc for hinic3 Feifei Wang
2025-05-20 15:30   ` Stephen Hemminger [this message]
2025-04-18  7:02 ` [RFC 10/18] net/hinic3: add context and work queue support Feifei Wang
2025-04-18  7:02 ` [RFC 11/18] net/hinic3: add a mailbox communication module Feifei Wang
2025-04-18  7:02 ` [RFC 12/18] net/hinic3: add device initailization Feifei Wang
2025-04-18  7:02 ` [RFC 13/18] net/hinic3: add dev ops Feifei Wang
2025-04-18  7:02 ` [RFC 14/18] net/hinic3: add Rx/Tx functions Feifei Wang
2025-04-18  7:02 ` [RFC 15/18] net/hinic3: add MML and EEPROM access feature Feifei Wang
2025-04-18  7:02 ` [RFC 16/18] net/hinic3: add RSS promiscuous ops Feifei Wang
2025-04-18  7:02 ` [RFC 17/18] net/hinic3: add FDIR flow control module Feifei Wang
2025-04-18  7:02 ` [RFC 18/18] drivers/net: add hinic3 PMD build and doc files Feifei Wang
2025-05-20 15:47 ` [RFC 00/18] add hinic3 PMD driver Stephen Hemminger
2025-04-18  8:08 Feifei Wang
2025-04-18  8:08 ` [RFC 01/18] net/hinic3: add intro doc for hinic3 Feifei Wang
2025-04-18  9:05 [RFC 00/18] add hinic3 PMD driver Feifei Wang
2025-04-18  9:05 ` [RFC 01/18] net/hinic3: add intro doc for hinic3 Feifei 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=20250520083027.45f5077c@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=chenyi221@huawei.com \
    --cc=dev@dpdk.org \
    --cc=wangfeifei40@huawei.com \
    --cc=wangxin679@h-partners.com \
    --cc=wff_light@vip.163.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).