DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Wang, Haiyue" <haiyue.wang@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Matan Azrad <matan@mellanox.com>,
	"Bie, Tiwei" <tiwei.bie@intel.com>,
	"Wang, Zhihong" <zhihong.wang@intel.com>,
	"Wang, Xiao W" <xiao.w.wang@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH v2 3/3] drivers: move ifc driver to the vDPA class
Date: Fri, 10 Jan 2020 19:17:14 +0000	[thread overview]
Message-ID: <3a921f8c-2744-2329-ead5-dc963cb2288a@redhat.com> (raw)
In-Reply-To: <1762954.eGJsNajkDb@xps>

On 10/01/2020 12:59, Thomas Monjalon wrote:
> 10/01/2020 13:34, Maxime Coquelin:
>> On 1/10/20 1:31 PM, Wang, Haiyue wrote:
>>> From: Thomas Monjalon <thomas@monjalon.net>
>>>> 10/01/2020 10:07, Matan Azrad:
>>>>> From: Wang, Haiyue
>>>>>> From: Matan Azrad
>>>>>>>>  delete mode 100644 doc/guides/nics/ifc.rst  create mode 100644
>>>>>>>> doc/guides/vdpadevs/features/ifcvf.ini
>>>>>>>>  create mode 100644 doc/guides/vdpadevs/ifc.rst  delete mode 100644
>>>>>>>> drivers/net/ifc/Makefile  delete mode 100644
>>>>>>>> drivers/net/ifc/base/ifcvf.c  delete mode 100644
>>>>>>>> drivers/net/ifc/base/ifcvf.h  delete mode 100644
>>>>>>>> drivers/net/ifc/base/ifcvf_osdep.h
>>>>>>>>  delete mode 100644 drivers/net/ifc/ifcvf_vdpa.c  delete mode 100644
>>>>>>>> drivers/net/ifc/meson.build  delete mode 100644
>>>>>>>> drivers/net/ifc/rte_pmd_ifc_version.map
>>>>>>>>  create mode 100644 drivers/vdpa/ifc/Makefile  create mode 100644
>>>>>>>> drivers/vdpa/ifc/base/ifcvf.c  create mode 100644
>>>>>>>> drivers/vdpa/ifc/base/ifcvf.h  create mode 100644
>>>>>>>> drivers/vdpa/ifc/base/ifcvf_osdep.h
>>>>>>>>  create mode 100644 drivers/vdpa/ifc/ifcvf_vdpa.c  create mode
>>>>>>>> 100644 drivers/vdpa/ifc/meson.build  create mode 100644
>>>>>>>> drivers/vdpa/ifc/rte_pmd_ifc_version.map
>>>>>>>>
>>>>>>
>>>>>> git mv drivers/net/ifc/ drivers/vdpa/ifc  ? ;-)
>>>>>
>>>>> Yes, and more file move in docs. (you can see like rename in git 😊)
>>>>> Adjusted also the classes makefiles\measons to remove from net and to add in vdpa.
>>>>> Also MAINTAINER file etc...
>>>>
>>>> I think the comment from Haiyue was about the files deleted and created
>>>> in the patch, instead of being moved (renamed).
>>>
>>> Yes, I moved one Intel PMD code, then the patch is very small, it is like:
>>>
>>>  rename drivers/{net/iavf/base => common/iavf}/iavf_common.c (100%)
>>>  rename drivers/{net/iavf/base => common/iavf}/iavf_devids.h (100%)
>>>
>>> detail is : https://patchwork.dpdk.org/patch/64384/
>>
>> Nice, and the advantage of doing so is that git would be smarter when
>> doing backport to stable branch.
> 
> No, git won't be smarter.
> As explained below, the format of the diff does not change the internal
> git representation of the change.
> Move/Rename is just a nice formatting done by smart detection.
> 

+1. Thanks for considering it, just checked and confirmed this with a
test backport on one of the "moved" files. (btw, see stats when patch is
applied with git version 2.21.1.)

 MAINTAINERS                                       | 14 ++++++--------
 doc/guides/nics/index.rst                         |  1 -
 doc/guides/{nics => vdpadevs}/features/ifcvf.ini  |  0
 doc/guides/{nics => vdpadevs}/ifc.rst             |  0
 doc/guides/vdpadevs/index.rst                     |  1 +
 drivers/net/Makefile                              |  3 ---
 drivers/net/meson.build                           |  1 -
 drivers/vdpa/Makefile                             |  6 ++++++
 drivers/{net => vdpa}/ifc/Makefile                |  0
 drivers/{net => vdpa}/ifc/base/ifcvf.c            |  0
 drivers/{net => vdpa}/ifc/base/ifcvf.h            |  0
 drivers/{net => vdpa}/ifc/base/ifcvf_osdep.h      |  0
 drivers/{net => vdpa}/ifc/ifcvf_vdpa.c            |  0
 drivers/{net => vdpa}/ifc/meson.build             |  0
 drivers/{net => vdpa}/ifc/rte_pmd_ifc_version.map |  0
 drivers/vdpa/meson.build                          |  2 +-
 16 files changed, 14 insertions(+), 14 deletions(-)


>>>> As far as I know, this is for 2 reasons:
>>>> 	- there is no move in internal git representation
>>>> 	- some versions of git-diff does not detect moves properly,
>>>> 	  but option -M may help
> 
> 
> 


  reply	other threads:[~2020-01-10 19:17 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 15:19 [dpdk-dev] [PATCH v1 0/3] Introduce new class for vDPA device drivers Matan Azrad
2019-12-25 15:19 ` [dpdk-dev] [PATCH v1 1/3] drivers: introduce vDPA class Matan Azrad
2020-01-07 17:32   ` Maxime Coquelin
2020-01-08 21:28     ` Thomas Monjalon
2020-01-09  8:00       ` Maxime Coquelin
2019-12-25 15:19 ` [dpdk-dev] [PATCH v1 2/3] doc: add vDPA feature table Matan Azrad
2020-01-07 17:39   ` Maxime Coquelin
2020-01-08  5:28     ` Tiwei Bie
2020-01-08  7:20       ` Andrew Rybchenko
2020-01-08 10:42         ` Matan Azrad
2020-01-08 13:11           ` Andrew Rybchenko
2020-01-08 17:01             ` Matan Azrad
2020-01-09  2:15           ` Tiwei Bie
2020-01-09  8:08             ` Matan Azrad
2019-12-25 15:19 ` [dpdk-dev] [PATCH v1 3/3] drivers: move ifc driver to the vDPA class Matan Azrad
2020-01-07 18:17   ` Maxime Coquelin
2020-01-07  7:57 ` [dpdk-dev] [PATCH v1 0/3] Introduce new class for vDPA device drivers Matan Azrad
2020-01-08  5:44   ` Xu, Rosen
2020-01-08 10:45     ` Matan Azrad
2020-01-08 12:39       ` Xu, Rosen
2020-01-08 12:58         ` Thomas Monjalon
2020-01-09  2:27           ` Xu, Rosen
2020-01-09  8:41             ` Thomas Monjalon
2020-01-09  9:23               ` Maxime Coquelin
2020-01-09  9:49                 ` Xu, Rosen
2020-01-09 10:42                   ` Maxime Coquelin
2020-01-10  2:40                     ` Xu, Rosen
2020-01-09 10:42                   ` Maxime Coquelin
2020-01-09 10:53               ` Xu, Rosen
2020-01-09 11:34                 ` Matan Azrad
2020-01-10  2:38                   ` Xu, Rosen
2020-01-10  9:21                     ` Thomas Monjalon
2020-01-10 14:18                       ` Xu, Rosen
2020-01-10 16:27                         ` Thomas Monjalon
2020-01-09 11:00 ` [dpdk-dev] [PATCH v2 " Matan Azrad
2020-01-09 11:00   ` [dpdk-dev] [PATCH v2 1/3] drivers: introduce vDPA class Matan Azrad
2020-01-09 11:00   ` [dpdk-dev] [PATCH v2 2/3] doc: add vDPA feature table Matan Azrad
2020-01-10 18:26     ` Thomas Monjalon
2020-01-13 22:40     ` Thomas Monjalon
2020-01-09 11:00   ` [dpdk-dev] [PATCH v2 3/3] drivers: move ifc driver to the vDPA class Matan Azrad
2020-01-09 17:25     ` Matan Azrad
2020-01-10  1:55       ` Wang, Haiyue
2020-01-10  9:07         ` Matan Azrad
2020-01-10  9:13           ` Thomas Monjalon
2020-01-10 12:31             ` Wang, Haiyue
2020-01-10 12:34               ` Maxime Coquelin
2020-01-10 12:59                 ` Thomas Monjalon
2020-01-10 19:17                   ` Kevin Traynor [this message]
2020-01-13 22:57     ` Thomas Monjalon
2020-01-13 23:08   ` [dpdk-dev] [PATCH v2 0/3] Introduce new class for vDPA device drivers 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=3a921f8c-2744-2329-ead5-dc963cb2288a@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=haiyue.wang@intel.com \
    --cc=matan@mellanox.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=tiwei.bie@intel.com \
    --cc=xiao.w.wang@intel.com \
    --cc=zhihong.wang@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).