Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "James Hogan" <james.hogan@imgtec.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH 01/14] MIPS: uasm: Add CFC1/CTC1 instructions
Date: Tue, 5 Jul 2016 16:04:56 +0200	[thread overview]
Message-ID: <20160705140456.GM7075@linux-mips.org> (raw)
In-Reply-To: <1f659139-ff8a-0291-eec3-9279d4ee9d60@redhat.com>

On Tue, Jul 05, 2016 at 03:56:31PM +0200, Paolo Bonzini wrote:

> On 23/06/2016 18:34, James Hogan wrote:
> > diff --git a/arch/mips/mm/uasm.c b/arch/mips/mm/uasm.c
> > index ad718debc35a..4731893db3f7 100644
> > --- a/arch/mips/mm/uasm.c
> > +++ b/arch/mips/mm/uasm.c
> > @@ -49,18 +49,18 @@ enum opcode {
> 
> This "enum opcode" looks like a pretty bad conflict magnet.  Ralf, can
> you check if you have any patches affecting it too?

Nothing at this point.

  Ralf

  reply	other threads:[~2016-07-05 14:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 16:34 [PATCH 00/14] MIPS: KVM: Dynamically generate exception code James Hogan
2016-06-23 16:34 ` James Hogan
2016-06-23 16:34 ` [PATCH 01/14] MIPS: uasm: Add CFC1/CTC1 instructions James Hogan
2016-06-23 16:34   ` James Hogan
2016-07-05 13:56   ` Paolo Bonzini
2016-07-05 14:04     ` Ralf Baechle [this message]
2016-06-23 16:34 ` [PATCH 02/14] MIPS: uasm: Add CFCMSA/CTCMSA instructions James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 03/14] MIPS: uasm: Add DI instruction James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 04/14] MIPS: uasm: Add MTHI/MTLO instructions James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 05/14] MIPS: uasm: Add r6 MUL encoding James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 06/14] MIPS; KVM: Convert exception entry to uasm James Hogan
2016-06-23 16:34   ` James Hogan
2016-07-04 18:53   ` James Hogan
2016-07-04 18:53     ` James Hogan
2016-06-23 16:34 ` [PATCH 07/14] MIPS: KVM: Add dumping of generated entry code James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 08/14] MIPS: KVM: Drop now unused asm offsets James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 09/14] MIPS: KVM: Omit FPU handling entry code if possible James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 10/14] MIPS: KVM: Check MSA presence at uasm time James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 11/14] MIPS: KVM: Drop redundant restore of DDATA_LO James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 12/14] MIPS: KVM: Dynamically choose scratch registers James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 13/14] MIPS: KVM: Relative branch to common exit handler James Hogan
2016-06-23 16:34   ` James Hogan
2016-06-23 16:34 ` [PATCH 14/14] MIPS: KVM: Save k0 straight into VCPU structure James Hogan
2016-06-23 16:34   ` James Hogan
2016-07-05 13:48 ` [PATCH 00/14] MIPS: KVM: Dynamically generate exception code Ralf Baechle
2016-07-05 13:53   ` Paolo Bonzini

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=20160705140456.GM7075@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=james.hogan@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox