WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH 0/3] xen: Use PM/Hibernate events for save/re

To: "Rafael J. Wysocki" <rjw@xxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 0/3] xen: Use PM/Hibernate events for save/restore/chkpt
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 28 Feb 2011 11:06:19 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Wilk <konrad.wilk@xxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Konrad, Pavel Machek <pavel@xxxxxx>, Shriram Rajagopalan <rshriram@xxxxxxxxx>, "linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx" <linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 28 Feb 2011 03:13:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201102251924.47802.rjw@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1298157158-5421-1-git-send-email-rshriram@xxxxxxxxx> <201102241941.00984.rjw@xxxxxxx> <alpine.DEB.2.00.1102251713560.19277@kaball-desktop> <201102251924.47802.rjw@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Fri, 25 Feb 2011, Rafael J. Wysocki wrote:
> On Friday, February 25, 2011, Stefano Stabellini wrote:
> > On Thu, 24 Feb 2011, Rafael J. Wysocki wrote:
> > > > I believe it only "[PATCH 3/3] PM: pm.h - Add comments about Xen 
> > > > save/restore/chkpt use case"
> > > > 
> > > > (http://marc.info/?i=1298157158-5421-4-git-send-email-rshriram@xxxxxxxxx)
> > > 
> > > This particular one should go in _after_ the functional patches.
> > > 
> > > > I or Stefano (these patches are against Ian's tree which is againsts 
> > > > Stefano's
> > > > tree) can take the other patches and stick Pavel's Ack, Rafeal's Ack, 
> > > > Ian's Ack
> > > > on them and also my Signed-off for the Xen bits.
> > > > 
> > > > I think that would work?
> > > 
> > > In fact, I think it's better if all patches go through the Xen tree.
> > > 
> >  
> > I don't mind taking them but if they have to go after your
> > suspend-2.6/linux-next tree this would introduce a new dependency in the
> > branch I am preparing for linux-next myself.
> > 
> > Should I pull your suspend-2.6/linux-next tree into my linux-next branch?
> > Considering that this could create conflicts in linux-next if you
> > force-push your tree with some new changes and I don't update my version
> > of it, maybe it is better if I pull only a reduced version of it with
> > just the strict dependencies?
> 
> It's not that simple, I think you'd need to pull my entire linux-next branch
> because of the dependencies between commits in there.
> 
> Alternatively, I can take the entire $subject patchset.
> 
> Still, I'd like the discussion to settle before anyway.
 
Ok then, when the discussion (and the code) is completely settled I'll
ask you if it is alright for me to pull your branch and have both in
linux-next.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel