From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38156)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <voipio@kos.to>) id 1bnjrp-0001e2-FR
	for qemu-devel@nongnu.org; Sat, 24 Sep 2016 06:07:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <voipio@kos.to>) id 1bnjrm-0001Ks-5Z
	for qemu-devel@nongnu.org; Sat, 24 Sep 2016 06:07:33 -0400
Received: from jessie.kos.to ([212.47.231.226]:37768 helo=pilvi.kos.to)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <voipio@kos.to>) id 1bnjrl-0001ID-Ux
	for qemu-devel@nongnu.org; Sat, 24 Sep 2016 06:07:30 -0400
Date: Sat, 24 Sep 2016 10:07:23 +0000
From: Riku Voipio <riku.voipio@iki.fi>
Message-ID: <20160924100723.GB11666@kos.to>
References: <20160919114456.66629-1-aleksandar.markovic@rt-rk.com>
	<20160921131654.GA18256@hhmipssw201.hh.imgtec.org>
	<20160921191220.GD24113@kos.to>
	<20160922062435.GA21330@hhmipssw201.hh.imgtec.org>
	<20160924100528.GA11666@kos.to>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160924100528.GA11666@kos.to>
Subject: Re: [Qemu-devel] [PATCH v7 0/7] linux-user: Fix miscellaneous
 Mips-specific issues
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: Leon Alrae <leon.alrae@imgtec.com>
Cc: qemu-devel@nongnu.org

On Sat, Sep 24, 2016 at 10:05:28AM +0000, Riku Voipio wrote:
> On Thu, Sep 22, 2016 at 07:24:36AM +0100, Leon Alrae wrote:
> > > > Applied to target-mips queue, thanks.
>  
> > > That's a bit unorthodox way but you have my acked-by then..
>  
> > Since these are mips-specific fixes I assumed it doesn't really matter
> > whether it goes via your or my tree (I picked up a few patches like
> > this in the past). Anyway, thanks for ack and next time I'll check with you.
> 
> The main risk here is that the patches conflict with other patches in
> linux-user/ directory, creating potential for merge conflict. Which
> unfortunately might be the case right now, as the main linux-user patchset
> was already merged..

I see it's merged already - sorry for the noise..

Riku