From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] mach-virt platform code for 3.9
Date: Sat, 09 Feb 2013 13:37:27 +0100 [thread overview]
Message-ID: <0696c7229c3499755984da15b64a877a@localhost> (raw)
In-Reply-To: <510FF8DC.6080202@arm.com>
On Mon, 04 Feb 2013 18:07:24 +0000, Marc Zyngier <marc.zyngier@arm.com>
wrote:
> On 04/02/13 13:55, Will Deacon wrote:
>> NOTE: I'm not suggesting you pull this one as it stands -- see below!
>>
>> This is the last batch from me (Marc is dealing with vgic and virtual
>> timers) and introduces support for mach-virt. This depends on:
>>
>> - for-arm-soc/arch-timers (third pull request in this series)
>> - for-rmk/virt/psci (already pulled)
>> - irqchip/gic-vic-move (an arm-soc branch)
>>
>> As a result, the diffstat is atrocious so it would be better if you
>> could create a branch merging the above dependendies, which I could
>> rebase onto (there's actually only two patches here).
>
> The remaining of the KVM/ARM code (vgic and timer) has exactly the same
> problem, plus an additional dependency on the actual kvm/core branch
> that Russell just pulled.
>
> I can either send you two pull requests that will basically look like
> this one (actually, a lot worse), or you could create a stable branch
> containing:
>
> - for-rmk/virt/kvm/core (first pull request in the series)
> - for-arm-soc/arch-timers (third pull request in the series)
> - irqchip/gic-vic-move (already in arm-soc)
>
> You could either create two stable branches (one for mach-virt and one
> for kvm-arm/{vgic,timer}), or a single one containing all the
> prerequisites.
>
> What do you think?
Arnd, Olof,
Any hope we can get branches for these? Now that the KVM core code is in
Russell's devel-stable branch, it would be a shame not to have the complete
thing...
Thanks,
M.
--
Fast, cheap, reliable. Pick two.
next prev parent reply other threads:[~2013-02-09 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 13:55 [GIT PULL 1/4] core ARM kvm implementation for 3.9 Will Deacon
2013-02-04 13:55 ` [GIT PULL 2/4] ARM broadcast timer updates " Will Deacon
2013-02-04 15:24 ` Russell King - ARM Linux
2013-02-05 22:37 ` Olof Johansson
2013-02-07 12:15 ` Will Deacon
2013-02-04 13:55 ` [GIT PULL 3/4] Move arch-timer into drivers/clocksource " Will Deacon
2013-02-04 13:55 ` [GIT PULL 4/4] mach-virt platform code " Will Deacon
2013-02-04 18:07 ` Marc Zyngier
2013-02-09 12:37 ` Marc Zyngier [this message]
2013-02-06 22:21 ` Rob Herring
2013-02-07 10:02 ` Will Deacon
2013-02-11 17:27 ` Olof Johansson
2013-02-11 17:47 ` Will Deacon
2013-02-11 18:42 ` Olof Johansson
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=0696c7229c3499755984da15b64a877a@localhost \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).