DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Leyi Rong <leyi.rong@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes for iavf renaming
Date: Tue, 26 Feb 2019 10:42:35 +0000	[thread overview]
Message-ID: <a441a8b4-7570-11f4-b71d-47c688467540@intel.com> (raw)
In-Reply-To: <20190226175840.36535-1-leyi.rong@intel.com>

On 2/26/2019 5:58 PM, Leyi Rong wrote:
> Update DPDK 19.05 release notes for iavf renaming.
> 
> Signed-off-by: Leyi Rong <leyi.rong@intel.com>
> ---
>  doc/guides/rel_notes/release_19_05.rst | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/guides/rel_notes/release_19_05.rst b/doc/guides/rel_notes/release_19_05.rst
> index c0390ca16..9042aecf6 100644
> --- a/doc/guides/rel_notes/release_19_05.rst
> +++ b/doc/guides/rel_notes/release_19_05.rst
> @@ -67,9 +67,15 @@ New Features
>  
>  * **Updated Mellanox drivers.**
>  
> -   New features and improvements were done in mlx4 and mlx5 PMDs:
> +  New features and improvements were done in mlx4 and mlx5 PMDs:
>  
> -   * Added firmware version reading.
> +  * Added firmware version reading.

Above changes are unrelated to this patch, ignoring them.

> +
> +* **Renamed avf to iavf.**
> +
> +  Renamed Intel Ethernet Adaptive Virtual Function driver ``avf`` to ``iavf``,
> +  which includes the directory name, lib name, filenames, makefile, docs,
> +  macros, functions, structs and any other strings in the code.
>  
>  
>  Removed Items
> 

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Squashed into relevant commit in next-net [1], thanks.

[1]: Commit "net/iavf: rename remaining avf strings"

      reply	other threads:[~2019-02-26 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 17:58 Leyi Rong
2019-02-26 10:42 ` Ferruh Yigit [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=a441a8b4-7570-11f4-b71d-47c688467540@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=leyi.rong@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).