From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [GIT PULL] (xen) pm-bug-fixes for 2.6.32
Date: Mon, 21 Mar 2011 16:20:51 +0000 [thread overview]
Message-ID: <4D877AE3.5070202@goop.org> (raw)
In-Reply-To: <AANLkTinNsuuAQxzAc=-PK6tCEbEBJNaPgK0xV0r=DofT@mail.gmail.com>
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?
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
next prev parent reply other threads:[~2011-03-21 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 3:13 [GIT PULL] (xen) pm-bug-fixes for 2.6.32 Shriram Rajagopalan
2011-03-21 16:20 ` Jeremy Fitzhardinge [this message]
2011-03-21 23:10 ` Shriram Rajagopalan
2011-03-22 13:43 ` Ian Campbell
2011-03-22 14:15 ` Shriram Rajagopalan
2011-03-22 16:45 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D877AE3.5070202@goop.org \
--to=jeremy@goop.org \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.