From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Leyi Rong <leyi.rong@intel.com>,
jingjing.wu@intel.com, wenzhuo.lu@intel.com,
qi.z.zhang@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: rename avf to iavf
Date: Fri, 22 Feb 2019 16:46:23 +0000 [thread overview]
Message-ID: <6447f339-c0a9-9b81-de89-a7d235b6c1e7@intel.com> (raw)
In-Reply-To: <20190222150336.22299-2-leyi.rong@intel.com>
On 2/22/2019 3:03 PM, Leyi Rong wrote:
> This patch renames avf to iavf only for the doc files.
>
> Signed-off-by: Leyi Rong <leyi.rong@intel.com>
> ---
> MAINTAINERS | 6 +++---
> doc/guides/nics/features/{avf.ini => iavf.ini} | 2 +-
> .../nics/features/{avf_vec.ini => iavf_vec.ini} | 2 +-
> doc/guides/nics/intel_vf.rst | 14 +++++++-------
> 4 files changed, 12 insertions(+), 12 deletions(-)
> rename doc/guides/nics/features/{avf.ini => iavf.ini} (93%)
> rename doc/guides/nics/features/{avf_vec.ini => iavf_vec.ini} (92%)
Normally I believe no need to make this a separate patch, but perhaps can be OK
to separate since first one is too big.
If the suggestion I make to separate renaming files, and updating file content
makes those patches smaller, I suggest squashing this patch that one.
next prev parent reply other threads:[~2019-02-22 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 15:03 [dpdk-dev] [PATCH 1/2] net/iavf: " Leyi Rong
2019-02-22 15:03 ` [dpdk-dev] [PATCH 2/2] doc: " Leyi Rong
2019-02-22 16:46 ` Ferruh Yigit [this message]
2019-02-24 8:51 ` Rong, Leyi
2019-02-25 17:18 ` [dpdk-dev] [PATCH v2 0/3] " Leyi Rong
2019-02-25 12:10 ` Ferruh Yigit
2019-02-25 17:18 ` [dpdk-dev] [PATCH v2 1/3] net/iavf: " Leyi Rong
2019-02-25 17:18 ` [dpdk-dev] [PATCH v2 2/3] net/iavf: rename remaining avf strings Leyi Rong
2019-02-25 17:18 ` [dpdk-dev] [PATCH v2 3/3] doc: rename avf to iavf Leyi Rong
2019-02-25 11:34 ` Ferruh Yigit
2019-02-22 16:43 ` [dpdk-dev] [PATCH 1/2] net/iavf: " Ferruh Yigit
2019-02-24 8:35 ` Rong, Leyi
2019-02-24 15:29 ` Rong, Leyi
2019-02-22 16:44 ` Ferruh Yigit
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=6447f339-c0a9-9b81-de89-a7d235b6c1e7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=leyi.rong@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@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).