|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [GIT PULL] (xen) pm-bug-fixes for 2.6.32
On Mon, Mar 21, 2011 at 9:20 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> <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
|
|
|
|
|