xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jan Beulich <JBeulich@novell.com>,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Pavel Machek <pavel@ucw.cz>,
	Shriram Rajagopalan <rshriram@cs.ubc.ca>,
	"linux-pm@lists.linux-foundation.org"
	<linux-pm@lists.linux-foundation.org>
Subject: Re: Re: [PATCH 0/3] xen: Use PM/Hibernate events for save/restore/chkpt
Date: Fri, 25 Feb 2011 19:24:47 +0100	[thread overview]
Message-ID: <201102251924.47802.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.DEB.2.00.1102251713560.19277@kaball-desktop>

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@cs.ubc.ca)
> > 
> > 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.

Thanks,
Rafael

  reply	other threads:[~2011-02-25 18:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19 23:12 [PATCH 0/3] xen: Use PM/Hibernate events for save/restore/chkpt Shriram Rajagopalan
2011-02-19 23:12 ` [PATCH 1/3] xen: xenbus PM events support Shriram Rajagopalan
2011-02-19 23:12 ` [PATCH 2/3] xen: use freeze/restore/thaw PM events for suspend/resume/chkpt Shriram Rajagopalan
2011-02-22 20:43   ` Konrad Rzeszutek Wilk
2011-02-22 21:14     ` Rafael J. Wysocki
2011-02-22 22:09     ` Shriram Rajagopalan
2011-02-22 22:35       ` Rafael J. Wysocki
2011-02-22 22:36       ` Konrad Rzeszutek Wilk
2011-02-22 22:53         ` Shriram Rajagopalan
2011-02-19 23:12 ` [PATCH 3/3] PM: pm.h - Add comments about Xen save/restore/chkpt use case Shriram Rajagopalan
2011-02-20  7:49 ` [PATCH 0/3] xen: Use PM/Hibernate events for save/restore/chkpt Pavel Machek
2011-02-21 10:05   ` Ian Campbell
2011-02-21 16:40     ` [linux-pm] " Alan Stern
2011-02-21 17:17       ` Ian Campbell
2011-02-21 20:23         ` Rafael J. Wysocki
2011-02-25 16:17           ` Stefano Stabellini
2011-02-25 16:19             ` Ian Campbell
2011-02-25 16:23               ` Stefano Stabellini
2011-02-23 18:38     ` Pavel Machek
2011-02-23 20:10       ` Rafael J. Wysocki
2011-02-24 16:13         ` Konrad Rzeszutek Wilk
2011-02-24 18:41           ` Rafael J. Wysocki
2011-02-25 17:19             ` Stefano Stabellini
2011-02-25 18:24               ` Rafael J. Wysocki [this message]
2011-02-28 11:06                 ` [Xen-devel] " Stefano Stabellini
2011-03-04 16:04                   ` Shriram Rajagopalan
2011-03-04 20:52                     ` Rafael J. Wysocki
2011-02-23  7:03 ` [PATCH v2 2/3] xen: use freeze/restore/thaw PM events for suspend/resume/chkpt Shriram Rajagopalan

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=201102251924.47802.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rshriram@cs.ubc.ca \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).