From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Olof Johansson <olof@lixom.net>, <arnd@arndb.de>
Subject: Re: [PATCH v5 0/4] xen/arm: CONFIG_PARAVIRT and stolen ticks accounting
Date: Mon, 3 Jun 2013 16:34:20 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1306031634050.4589@kaball.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305301426520.4799@kaball.uk.xensource.com>
On Thu, 30 May 2013, Stefano Stabellini wrote:
> I am starting to be pretty confident about this patch series.
>
> Please advice on what tree I should use to get this stuff upstream: most
> of the changes are Xen specific, but it also contains few generic ARM
> changes (the introduction of CONFIG_PARAVIRT and paravirt.c on ARM) and
> a couple of lines in kernel/sched/cputime.c (a missing include).
ping?
prev parent reply other threads:[~2013-06-03 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 13:33 Stefano Stabellini
2013-05-30 13:34 ` [PATCH v5 1/4] xen: move xen_setup_runstate_info and get_runstate_snapshot to drivers/xen/time.c Stefano Stabellini
2013-05-30 13:35 ` [PATCH v5 2/4] kernel: missing include in cputime.c Stefano Stabellini
2013-06-05 17:30 ` Stefano Stabellini
2013-05-30 13:35 ` [PATCH v5 3/4] arm: introduce CONFIG_PARAVIRT, PARAVIRT_TIME_ACCOUNTING and pv_time_ops Stefano Stabellini
2013-06-05 17:27 ` Stefano Stabellini
2013-05-30 13:35 ` [PATCH v5 4/4] xen/arm: account for stolen ticks Stefano Stabellini
2013-06-03 15:34 ` Stefano Stabellini [this message]
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=alpine.DEB.2.02.1306031634050.4589@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=arnd@arndb.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=olof@lixom.net \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®