From: "Rong, Leyi" <leyi.rong@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: rename avf to iavf
Date: Sun, 24 Feb 2019 08:51:49 +0000 [thread overview]
Message-ID: <47ACC7359E973C41ACB0C2477632BC725186B69C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <6447f339-c0a9-9b81-de89-a7d235b6c1e7@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Saturday, February 23, 2019 12:46 AM
> To: Rong, Leyi <leyi.rong@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>;
> Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 2/2] doc: rename avf to iavf
>
> 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.
Hi Ferruh,
Can I just keep this patch as a separate one since this one will only affect the doc files, but the previous patch is a big one which will affect the iavf src code.
Thanks,
Leyi
next prev parent reply other threads:[~2019-02-24 8:51 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
2019-02-24 8:51 ` Rong, Leyi [this message]
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=47ACC7359E973C41ACB0C2477632BC725186B69C@SHSMSX103.ccr.corp.intel.com \
--to=leyi.rong@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@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).