From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: "Christoffer Dall" <cdall@cs.columbia.edu>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Marc Zyngier" <marc.zyngier@arm.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: linux-next: manual merge of the kvm-arm tree with Linus' tree
Date: Thu, 16 Apr 2015 21:39:06 +0200 [thread overview]
Message-ID: <55300FDA.1010606@redhat.com> (raw)
In-Reply-To: <20150416191044.GF6186@cbox>
On 16/04/2015 21:10, Christoffer Dall wrote:
>> >
> As it turns out, it was not the same logic as Stephen's resolution.
> Stephen's resolution is bussy, because vlr is passed by value to
> vgic_queue_irq_to_lr() and therefore the call to sync the elrsr does not
> have any effect.
>
> Unfortunately, it seems Paolo's more correct fix did not end up in
> Linus' tree, so I guess I should just send a patch?
Uhm, sure it did :)
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/virt/kvm/arm/vgic.c#n1121
Stephen's resolutions never end up in Linus's tree, as Stephen never
sends anything to Linus.
Paolo
next prev parent reply other threads:[~2015-04-16 19:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 3:41 linux-next: manual merge of the kvm-arm tree with Linus' tree Stephen Rothwell
2015-03-18 7:55 ` Christoffer Dall
2015-04-07 16:20 ` Paolo Bonzini
2015-04-08 8:15 ` Marc Zyngier
2015-04-08 10:57 ` Christoffer Dall
2015-04-16 19:10 ` Christoffer Dall
2015-04-16 19:39 ` Paolo Bonzini [this message]
2015-04-16 20:16 ` Christoffer Dall
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 2:38 Stephen Rothwell
2018-01-03 9:50 ` Christoffer Dall
2017-11-06 2:56 Stephen Rothwell
2017-11-06 2:52 Stephen Rothwell
2017-04-10 4:02 Stephen Rothwell
2017-04-10 8:02 ` Christoffer Dall
2014-10-17 1:47 Stephen Rothwell
2014-07-31 6:30 Stephen Rothwell
2014-07-31 12:10 ` Marc Zyngier
[not found] ` <CAEDV+gJ1oSPzgZMO=kdFDNPnzy-EOHGuLxHqTB8KO6d_8yPrxQ@mail.gmail.com>
2014-07-31 12:15 ` Marc Zyngier
2014-07-31 14:23 ` Christoffer Dall
2014-07-31 14:30 ` Marc Zyngier
2014-08-01 5:21 ` Stephen Rothwell
2014-07-31 12:17 ` Stephen Rothwell
2014-07-31 12:41 ` Stephen Rothwell
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=55300FDA.1010606@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cdall@cs.columbia.edu \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=sfr@canb.auug.org.au \
/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).