All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: James Hogan <james.hogan@imgtec.com>, <qemu-devel@nongnu.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
	Richard Henderson <rth@twiddle.net>,
	Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>
Subject: Re: [PATCH for 2.4 0/2] MIPS build fixes for v2.4
Date: Thu, 9 Jul 2015 12:52:07 +0100	[thread overview]
Message-ID: <559E6067.6040103@imgtec.com> (raw)
In-Reply-To: <1436433435-24898-1-git-send-email-james.hogan@imgtec.com>

On 09/07/2015 10:17, James Hogan wrote:
> These two patches fix build errors for the MIPS TCG backend and MIPS
> KVM.
> 
> Please could they be applied for v2.4.
> 
> James Hogan (2):
>   tcg/mips: Fix build error from merged memop+mmu_idx parameter
>   mips/kvm: Sync with newer MIPS KVM headers
> 
>  target-mips/kvm.c     | 15 ++-------------
>  tcg/mips/tcg-target.c |  4 ++--
>  2 files changed, 4 insertions(+), 15 deletions(-)

Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>

Peter, since these are build fixes, could they be squeezed into rc0?

Thanks,
Leon


WARNING: multiple messages have this Message-ID (diff)
From: Leon Alrae <leon.alrae@imgtec.com>
To: James Hogan <james.hogan@imgtec.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, Aurelien Jarno <aurelien@aurel32.net>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for 2.4 0/2] MIPS build fixes for v2.4
Date: Thu, 9 Jul 2015 12:52:07 +0100	[thread overview]
Message-ID: <559E6067.6040103@imgtec.com> (raw)
In-Reply-To: <1436433435-24898-1-git-send-email-james.hogan@imgtec.com>

On 09/07/2015 10:17, James Hogan wrote:
> These two patches fix build errors for the MIPS TCG backend and MIPS
> KVM.
> 
> Please could they be applied for v2.4.
> 
> James Hogan (2):
>   tcg/mips: Fix build error from merged memop+mmu_idx parameter
>   mips/kvm: Sync with newer MIPS KVM headers
> 
>  target-mips/kvm.c     | 15 ++-------------
>  tcg/mips/tcg-target.c |  4 ++--
>  2 files changed, 4 insertions(+), 15 deletions(-)

Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>

Peter, since these are build fixes, could they be squeezed into rc0?

Thanks,
Leon

  parent reply	other threads:[~2015-07-09 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  9:17 [PATCH for 2.4 0/2] MIPS build fixes for v2.4 James Hogan
2015-07-09  9:17 ` [Qemu-devel] " James Hogan
2015-07-09  9:17 ` [Qemu-devel] [PATCH for 2.4 1/2] tcg/mips: Fix build error from merged memop+mmu_idx parameter James Hogan
2015-07-09 13:58   ` Aurelien Jarno
2015-07-09  9:17 ` [PATCH for 2.4 2/2] mips/kvm: Sync with newer MIPS KVM headers James Hogan
2015-07-09  9:17   ` [Qemu-devel] " James Hogan
2015-07-09 11:52 ` Leon Alrae [this message]
2015-07-09 11:52   ` [Qemu-devel] [PATCH for 2.4 0/2] MIPS build fixes for v2.4 Leon Alrae
2015-07-09 13:59   ` Peter Maydell
2015-07-09 13:59     ` [Qemu-devel] " Peter Maydell
2015-07-09 14:28     ` James Hogan
2015-07-09 14:28       ` [Qemu-devel] " James Hogan

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=559E6067.6040103@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=aurelien@aurel32.net \
    --cc=james.hogan@imgtec.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.