From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43893)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Leon.Alrae@imgtec.com>) id 1XorcI-0006UD-7q
	for qemu-devel@nongnu.org; Thu, 13 Nov 2014 05:27:12 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Leon.Alrae@imgtec.com>) id 1Xorc9-0007NO-8t
	for qemu-devel@nongnu.org; Thu, 13 Nov 2014 05:27:06 -0500
Received: from mailapp01.imgtec.com ([195.59.15.196]:10051)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Leon.Alrae@imgtec.com>) id 1Xorc9-0007NJ-42
	for qemu-devel@nongnu.org; Thu, 13 Nov 2014 05:26:57 -0500
Message-ID: <54648751.8060404@imgtec.com>
Date: Thu, 13 Nov 2014 10:26:25 +0000
From: Leon Alrae <leon.alrae@imgtec.com>
MIME-Version: 1.0
References: <alpine.DEB.1.10.1411120328290.2881@tp.orcam.me.uk>
	<5463A426.1000502@suse.de>
	<alpine.DEB.1.10.1411121844430.2881@tp.orcam.me.uk>
In-Reply-To: <alpine.DEB.1.10.1411121844430.2881@tp.orcam.me.uk>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH] mips: Fix the 64-bit case for microMIPS
 MOVE16 and MOVEP
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Maciej W. Rozycki" <macro@codesourcery.com>, =?windows-1252?Q?Andrea?= =?windows-1252?Q?s_F=E4rber?= <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>

On 12/11/2014 18:46, Maciej W. Rozycki wrote:
> On Wed, 12 Nov 2014, Andreas F=E4rber wrote:
>=20
>> Please consistently use "target-mips: " when that's what you're
>> touching. (For hw/mips/ it's less consistent what to use.)
>=20
>  Sure.  What about MIPS changes that span files contained within=20
> target-mips/ and elsewhere?  I have such changes in my queue.

It might be a good idea to split these changes into separate patches to
have more precise indication about touched subsystem (even though all
the changes were done in MIPS context). For example "target-mips" and
"linux-user" rather than just "mips".

Regards,
Leon