All of lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL] VGIC fixes for KVM/ARM
Date: Fri, 22 Feb 2013 18:28:41 +0100	[thread overview]
Message-ID: <215351192187808fc309b8f9c0541b1c@localhost> (raw)
In-Reply-To: <20130222154136.GD17833@n2100.arm.linux.org.uk>

On Fri, 22 Feb 2013 15:41:36 +0000, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Fri, Feb 22, 2013 at 02:58:12PM +0100, Marc Zyngier wrote:
>> Arnd, Olof,
>> 
>> Please find below a pull request for a couple of fixes concerning
>> the VGIC implementation in KVM. No real hurry, these can probably
>> be applied after the merge window.
>> 
>> The branch is on top of mainline as of this morning, but I'm happy
>> to rebase it on something else if that's more convenient.
> 
> Now, why is this being thrown at arm-soc?  Is it not core ARM stuff,
> or is KVM being counted as yet another platform?

You're right. Arm-soc took care of the initial merge of the VGIC code
because of other dependencies, but now that it has been merged, I should
have sent the pull request to you. Sincere apologies.

Shall I send you another pull request, or would you prefer these patches
in the patch system?

Thanks,

        M.
-- 
Fast, cheap, reliable. Pick two.

  reply	other threads:[~2013-02-22 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 13:58 [PULL] VGIC fixes for KVM/ARM Marc Zyngier
2013-02-22 15:41 ` Russell King - ARM Linux
2013-02-22 17:28   ` Marc Zyngier [this message]
2013-02-22 19:18     ` Russell King - ARM Linux
2013-02-22 19:30       ` Marc Zyngier
2013-03-22 16:29         ` Marc Zyngier
2013-03-22 17:13           ` Russell King - ARM Linux
  -- strict thread matches above, loose matches on Subject: below --
2013-03-22 17:43 Marc Zyngier

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=215351192187808fc309b8f9c0541b1c@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 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.