From: Konrad Rzeszutek Wilk Subject: Re: Re: [PATCH 1/3] xen dom0: Add support for the platform_ops hypercall Date: Tue, 16 Nov 2010 10:52:58 -0500 Message-ID: <20101116155258.GB6535@dumpdata.com> References: <0aa82d86c699890ce3661927f176045fc8e47156.1289519130.git.jeremy.fitzhardinge@citrix.com> <20101115154814.GB345@dumpdata.com> <4CE1DB0F.8030808@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4CE1DB0F.8030808@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Xen-devel , Stephen Tweedie , the arch/x86 maintainers , Linux Kernel Mailing List , Jeremy Fitzhardinge , "H. Peter Anvin" List-Id: xen-devel@lists.xenproject.org > > Why not just introduce the one we are using (just one right now) > > and on subsequent patches that enable the functionality add it in this file? > > The main reason is that if some other branch also brings in platform.h > then its easier to merge two copies of the same file rather than two > subsets. Sure, but in linux-next that is just one touch patch and Stephen said he is Ok with those. I like doing it (just stick in those that we use), b/c that way you have an excellent view of when this feature went in the code and the relevant git commits to blame.