All of lore.kernel.org
 help / color / mirror / Atom feed
From: gleb@redhat.com (Gleb Natapov)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Fix vmalloc allocations for KVM/ARM
Date: Tue, 19 Nov 2013 10:29:07 +0200	[thread overview]
Message-ID: <20131119082907.GW2008@redhat.com> (raw)
In-Reply-To: <1384809194-9301-1-git-send-email-christoffer.dall@linaro.org>

On Mon, Nov 18, 2013 at 01:13:13PM -0800, Christoffer Dall wrote:
> Hi Gleb and Paolo,
> 
Pulled, thanks.

> Please pull this into kvm/master:
> 
> The following changes since commit 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52:
> 
>   Linux 3.12 (2013-11-03 15:41:51 -0800)
> 
> are available in the git repository at:
> 
>   git://git.linaro.org/people/cdall/linux-kvm-arm.git tags/kvm-arm-fixes-3.13-1
> 
> for you to fetch changes up to 40c2729bab48e2832b17c1fa8af9db60e776131b:
> 
>   arm/arm64: KVM: Fix hyp mappings of vmalloc regions (2013-11-16 18:54:45 -0800)
> 
> ----------------------------------------------------------------
> Fix percpu vmalloc allocations
> 
> ----------------------------------------------------------------
> Christoffer Dall (1):
>       arm/arm64: KVM: Fix hyp mappings of vmalloc regions
> 
>  arch/arm/kvm/mmu.c |   34 ++++++++++++++++++++++++++++------
>  1 file changed, 28 insertions(+), 6 deletions(-)

--
			Gleb.

WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [GIT PULL] Fix vmalloc allocations for KVM/ARM
Date: Tue, 19 Nov 2013 10:29:07 +0200	[thread overview]
Message-ID: <20131119082907.GW2008@redhat.com> (raw)
In-Reply-To: <1384809194-9301-1-git-send-email-christoffer.dall@linaro.org>

On Mon, Nov 18, 2013 at 01:13:13PM -0800, Christoffer Dall wrote:
> Hi Gleb and Paolo,
> 
Pulled, thanks.

> Please pull this into kvm/master:
> 
> The following changes since commit 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52:
> 
>   Linux 3.12 (2013-11-03 15:41:51 -0800)
> 
> are available in the git repository at:
> 
>   git://git.linaro.org/people/cdall/linux-kvm-arm.git tags/kvm-arm-fixes-3.13-1
> 
> for you to fetch changes up to 40c2729bab48e2832b17c1fa8af9db60e776131b:
> 
>   arm/arm64: KVM: Fix hyp mappings of vmalloc regions (2013-11-16 18:54:45 -0800)
> 
> ----------------------------------------------------------------
> Fix percpu vmalloc allocations
> 
> ----------------------------------------------------------------
> Christoffer Dall (1):
>       arm/arm64: KVM: Fix hyp mappings of vmalloc regions
> 
>  arch/arm/kvm/mmu.c |   34 ++++++++++++++++++++++++++++------
>  1 file changed, 28 insertions(+), 6 deletions(-)

--
			Gleb.

  parent reply	other threads:[~2013-11-19  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 21:13 [GIT PULL] Fix vmalloc allocations for KVM/ARM Christoffer Dall
2013-11-18 21:13 ` Christoffer Dall
2013-11-18 21:13 ` [PATCH] arm/arm64: KVM: Fix hyp mappings of vmalloc regions Christoffer Dall
2013-11-18 21:13   ` Christoffer Dall
2013-11-19  8:29 ` Gleb Natapov [this message]
2013-11-19  8:29   ` [GIT PULL] Fix vmalloc allocations for KVM/ARM Gleb Natapov

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=20131119082907.GW2008@redhat.com \
    --to=gleb@redhat.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.