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

[Xen-devel] Re: [GIT PULL] (xen) pm-bug-fixes for 2.6.32

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [GIT PULL] (xen) pm-bug-fixes for 2.6.32
From: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Date: Mon, 21 Mar 2011 16:10:50 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 21 Mar 2011 16:12:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D877AE3.5070202@xxxxxxxx>
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: <AANLkTinNsuuAQxzAc=-PK6tCEbEBJNaPgK0xV0r=DofT@xxxxxxxxxxxxxx> <4D877AE3.5070202@xxxxxxxx>
Reply-to: rshriram@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Mar 21, 2011 at 9:20 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
On 03/21/2011 03:13 AM, Shriram Rajagopalan wrote:
> Hi Jeremy,
>
> Can you please pull
>
> git://athos.nss.cs.ubc.ca/linux-2.6-pvops.git
> <http://athos.nss.cs.ubc.ca/linux-2.6-pvops.git> xen/pm-bug-fix
>
> #xen/pm-bug-fix is based off xen/next-2.6.32,
> commit ea954f6ff4ff5c15c9e2120e86335f6d6490ae0f
> "Merge commit 'konrad-xen/for-2.6.32/bug-fixes~1' into xen/next-2.6.32"
>
> All patches in this branch have been merged into upstream kernel.

Are they marked to go into the stable/longterm tree, or are we just
going to maintain them separately?

I think these should go into the longterm tree. I am a bit clueless as to what you
exactly mean by "maintaining them separately". I thought next-2.6.32 was meant
as a staging area, that later gets pushed to stable-2.6.32.x

Konrad/Ian ?

shriram
   J

>
> The diffstat:
>
>  drivers/xen/manage.c                       |   16 ++++++++--------
>  drivers/xen/xenbus/xenbus_probe.c          |   12 ++++++++++--
>  drivers/xen/xenbus/xenbus_probe.h          |    3 ++-
>  drivers/xen/xenbus/xenbus_probe_frontend.c |   26
> ++++++++++++++++----------
>  include/xen/xenbus.h                       |    2 +-
>  5 files changed, 37 insertions(+), 22 deletions(-)
>
> Kazuhiro SUZUKI (1):
>      xen: xenbus PM events support
>
> Shriram Rajagopalan (1):
>       xen: use freeze/restore/thaw PM events for suspend/resume/chkpt
>
> shriram


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