From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHBv0-0002Gw-CF for qemu-devel@nongnu.org; Fri, 30 Jan 2015 08:47:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YHBuw-0004gM-Bo for qemu-devel@nongnu.org; Fri, 30 Jan 2015 08:47:30 -0500 Received: from eddie.linux-mips.org ([148.251.95.138]:42931 helo=cvs.linux-mips.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHBuv-0004eN-Sr for qemu-devel@nongnu.org; Fri, 30 Jan 2015 08:47:26 -0500 Received: from localhost.localdomain ([127.0.0.1]:51396 "EHLO localhost.localdomain" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S27012290AbbA3NrRn2kQd (ORCPT ); Fri, 30 Jan 2015 14:47:17 +0100 Date: Fri, 30 Jan 2015 13:47:17 +0000 (GMT) From: "Maciej W. Rozycki" In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [Qemu-devel] [PATCH 0/7] MIPS: IEEE 754-2008 features support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Thomas Schwinge Cc: Leon Alrae , QEMU Developers , Aurelien Jarno On Fri, 30 Jan 2015, Peter Maydell wrote: > > This patch series comprises changes to QEMU, both the MIPS backend and > > generic SoftFloat support code, to support IEEE 754-2008 features > > introduced to revision 3.50 of the MIPS Architecture as follows. > > Just to let you know that: > (1) the softfloat relicensing has hit master, so this patchset isn't > blocked by anything now > (2) I would like to see a definite "we are happy to license this > patchset under the SoftFloat-2a license" for these changes, because > they were submitted before we applied the relicensing, and therefore > the "changes after $DATE will be -2a license unless otherwise stated" > note in the sourcecode can't be assumed to apply to them. Thanks for the heads-up! At this stage however someone at Mentor will have to make such a statement on behalf of the company as I am no longer there and as far as this patch set is concerned I am merely a member of the public who can just make technical comments as anyone can, including you. I think Thomas, being the writer of the majority of code comprising these patches, is now in the best position to make such a statement happen. Thomas -- will you be able to take it from here? Thanks! Maciej