From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Q: Clarification about extra option ..Re: Re: [PATCH] pvops: Make suspend work when CONFIG_SUSPEND=n Date: Tue, 8 Mar 2011 10:53:11 -0500 Message-ID: <20110308155311.GD20811@dumpdata.com> References: <201103042107.55975.rjw@sisk.pl> <201103062312.07555.rjw@sisk.pl> <20110307175325.GC4930@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Shriram Rajagopalan Cc: Ian Campbell , "xen-devel@lists.xensource.com" , Frank Pan , Jeremy Fitzhardinge , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org > I can do either. I can also post a link to my git tree, if that would make > your life easier (in terms > of merging, etc). Sure. > > > b). I am going to extract that branch in my tree > > c). You are going to post the patches that you had to develop so we can > > review > > them. > > > Just to confirm, I should post these patches against my *hybrid* tree > because neither > Stefano's nor Rafael's tree are suitable. :(. > > > d). If everybody is happy and testing on our test-beds is OK, I can push > > this tree > > later in the merge window cycle. > > > > so, when people test these patches, they would test it against your tree ? > (which would then > have incorporated my changes). Right. The idea is that I pull my tree, say #devel/next-2.6.38 and can just do 'git pull pv-on-hvm-fixes' and it applies cleanly and I can test it.