DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Qiming Yang <qiming.yang@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com
Subject: Re: [PATCH] doc: add release note for new e1000 device
Date: Tue, 13 Jun 2023 10:33:41 +0200	[thread overview]
Message-ID: <CAJFAV8x7RsMu4UWb7ce=0yT+NTf86_O-Bm1Z3MRJ7wLyOxaLvQ@mail.gmail.com> (raw)
In-Reply-To: <20230613075548.2290073-1-qiming.yang@intel.com>

On Tue, Jun 13, 2023 at 10:13 AM Qiming Yang <qiming.yang@intel.com> wrote:
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> ---
>  doc/guides/rel_notes/release_23_07.rst | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_23_07.rst b/doc/guides/rel_notes/release_23_07.rst
> index 027ae7bd2d..382dbfbe37 100644
> --- a/doc/guides/rel_notes/release_23_07.rst
> +++ b/doc/guides/rel_notes/release_23_07.rst
> @@ -170,6 +170,9 @@ New Features
>
>    See :doc:`../prog_guide/pdcp_lib` for more information.
>
> +* **Updated INTEL e1000 driver.**

Intel*

> +
> +  * Added support for new I219 devices.

Quoting the description a bit earlier in this same file:

"""
     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)
"""

Please move this update where appropriate.


>
>  Removed Items
>  -------------
> --
> 2.25.1
>


-- 
David Marchand


  reply	other threads:[~2023-06-13  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  7:55 Qiming Yang
2023-06-13  8:33 ` David Marchand [this message]
2023-06-28  3:20 ` [PATCH v2] doc: fix missing release note for I219 support Qiming Yang
2023-07-03  4:25   ` Zhang, Qi Z
2023-07-27 18:02     ` Thomas Monjalon

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='CAJFAV8x7RsMu4UWb7ce=0yT+NTf86_O-Bm1Z3MRJ7wLyOxaLvQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.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).