From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tamas K Lengyel Subject: Re: [RFC PATCH V3 05/12] xen: Introduce vm_event Date: Fri, 6 Feb 2015 15:01:08 +0100 Message-ID: References: <1422567998-29995-1-git-send-email-tamas.lengyel@zentific.com> <1422567998-29995-6-git-send-email-tamas.lengyel@zentific.com> <54D0FD39020000780005C792@mail.emea.novell.com> <54D4C883.70000@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54D4C883.70000@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper Cc: "Tian, Kevin" , "wei.liu2@citrix.com" , Ian Campbell , Razvan Cojocaru , Stefano Stabellini , Jun Nakajima , "Dong, Eddie" , Tim Deegan , "xen-devel@lists.xen.org" , Steven Maresca , Andres Lagar-Cavilla , Jan Beulich , "rshriram@cs.ubc.ca" , Keir Fraser , Daniel De Graaf , "yanghy@cn.fujitsu.com" , Ian Jackson List-Id: xen-devel@lists.xenproject.org On Fri, Feb 6, 2015 at 2:58 PM, Andrew Cooper wrote: > On 06/02/15 13:54, Tamas K Lengyel wrote: >>> Please clarify in the patch description whether this (and perhaps >>> other) copied or cloned code is really just a plain copy with some >>> renaming, or whether there are any other changes. Reviewing this >>> as a non-renaming change isn't time well spent in the former case. >> Ack, this code is identical to mem_event beside the name. > > Using git format-patch/diff -M will make this much more obvious by > creating a diff which looks something like: > > --- a/xen/common/mem_event.c > +++ b/xen/common/vm_event.c > > and contains hunks renaming the functions alone. > > ~Andrew I'll take a look at that, it would certainly simplify things. Tamas