From: Christoffer Dall <christoffer.dall@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: KVM: Turn kvm_ksym_ref into a NOP on VHE
Date: Mon, 21 Mar 2016 19:55:24 +0100 [thread overview]
Message-ID: <20160321185524.GD16859@cbox> (raw)
In-Reply-To: <56EFFEEB.8020800@redhat.com>
On Mon, Mar 21, 2016 at 03:02:19PM +0100, Paolo Bonzini wrote:
>
>
> On 21/03/2016 13:42, Christoffer Dall wrote:
> > Marc is on holiday this week, but I put this (with the fix) on top of
> > Linus' master in the kvmarm/master branch:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git master
> >
> > Do you want to just grab it from there?
>
> Since you have two more patches, I guess you can just send a pull
> request for all three. I plan to send mine to Linus on Wednesday.
>
Sounds good, I'll send you one tomorrow (based on Linus' master branch
of today - if that works?)
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: KVM: Turn kvm_ksym_ref into a NOP on VHE
Date: Mon, 21 Mar 2016 19:55:24 +0100 [thread overview]
Message-ID: <20160321185524.GD16859@cbox> (raw)
In-Reply-To: <56EFFEEB.8020800@redhat.com>
On Mon, Mar 21, 2016 at 03:02:19PM +0100, Paolo Bonzini wrote:
>
>
> On 21/03/2016 13:42, Christoffer Dall wrote:
> > Marc is on holiday this week, but I put this (with the fix) on top of
> > Linus' master in the kvmarm/master branch:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git master
> >
> > Do you want to just grab it from there?
>
> Since you have two more patches, I guess you can just send a pull
> request for all three. I plan to send mine to Linus on Wednesday.
>
Sounds good, I'll send you one tomorrow (based on Linus' master branch
of today - if that works?)
-Christoffer
next prev parent reply other threads:[~2016-03-21 18:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:25 [PATCH] arm64: KVM: Turn kvm_ksym_ref into a NOP on VHE Marc Zyngier
2016-03-18 17:25 ` Marc Zyngier
2016-03-18 17:41 ` Robin Murphy
2016-03-18 17:41 ` Robin Murphy
2016-03-18 18:07 ` Catalin Marinas
2016-03-18 18:07 ` Catalin Marinas
2016-03-20 21:07 ` Christoffer Dall
2016-03-20 21:07 ` Christoffer Dall
2016-03-21 11:34 ` Catalin Marinas
2016-03-21 11:34 ` Catalin Marinas
2016-03-21 8:47 ` Ard Biesheuvel
2016-03-21 8:47 ` Ard Biesheuvel
2016-03-21 12:36 ` Paolo Bonzini
2016-03-21 12:36 ` Paolo Bonzini
2016-03-21 12:42 ` Christoffer Dall
2016-03-21 12:42 ` Christoffer Dall
2016-03-21 14:02 ` Paolo Bonzini
2016-03-21 14:02 ` Paolo Bonzini
2016-03-21 18:55 ` Christoffer Dall [this message]
2016-03-21 18:55 ` Christoffer Dall
2016-03-21 20:55 ` Paolo Bonzini
2016-03-21 20:55 ` Paolo Bonzini
2016-03-22 7:33 ` Christoffer Dall
2016-03-22 7:33 ` Christoffer Dall
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=20160321185524.GD16859@cbox \
--to=christoffer.dall@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.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.