From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Shriram Rajagopalan <rshriram@cs.ubc.ca>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Frank Pan <frankpzh@gmail.com>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Q: Clarification about extra option ..Re: Re: [PATCH] pvops: Make suspend work when CONFIG_SUSPEND=n
Date: Tue, 8 Mar 2011 10:53:11 -0500 [thread overview]
Message-ID: <20110308155311.GD20811@dumpdata.com> (raw)
In-Reply-To: <AANLkTi=TJxEUzLn=dFqZsO4pvpmwUMtEvey1Y94vNeoD@mail.gmail.com>
> I can do either. I can also post a link to my git tree, if that would make
> your life easier (in terms
> of merging, etc).
Sure.
>
> > b). I am going to extract that branch in my tree
> > c). You are going to post the patches that you had to develop so we can
> > review
> > them.
> >
> Just to confirm, I should post these patches against my *hybrid* tree
> because neither
> Stefano's nor Rafael's tree are suitable. :(.
<nods>
>
> > d). If everybody is happy and testing on our test-beds is OK, I can push
> > this tree
> > later in the merge window cycle.
> >
> > so, when people test these patches, they would test it against your tree ?
> (which would then
> have incorporated my changes).
Right. The idea is that I pull my tree, say #devel/next-2.6.38 and can
just do 'git pull <url> pv-on-hvm-fixes' and it applies cleanly and I can
test it.
next prev parent reply other threads:[~2011-03-08 15:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 11:20 [PATCH] pvops: Make suspend work when CONFIG_SUSPEND=n Frank Pan
2011-03-04 11:35 ` Ian Campbell
2011-03-04 11:45 ` Frank Pan
2011-03-04 11:52 ` Ian Campbell
2011-03-04 15:42 ` Shriram Rajagopalan
2011-03-04 15:56 ` Konrad Rzeszutek Wilk
2011-03-04 16:29 ` Shriram Rajagopalan
2011-03-04 18:26 ` Q: Clarification about extra option ..Re: " Konrad Rzeszutek Wilk
2011-03-04 19:49 ` Shriram Rajagopalan
2011-03-04 20:07 ` Rafael J. Wysocki
2011-03-06 20:31 ` Shriram Rajagopalan
2011-03-06 22:12 ` Rafael J. Wysocki
2011-03-07 12:44 ` Stefano Stabellini
2011-03-07 16:33 ` Shriram Rajagopalan
2011-03-07 17:53 ` Konrad Rzeszutek Wilk
2011-03-07 18:17 ` Shriram Rajagopalan
2011-03-08 15:53 ` Konrad Rzeszutek Wilk [this message]
2011-03-07 17:39 ` Konrad Rzeszutek Wilk
2011-03-04 20:05 ` Rafael J. Wysocki
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=20110308155311.GD20811@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=frankpzh@gmail.com \
--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 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.