From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54702) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cmJBz-0001Re-TA for qemu-devel@nongnu.org; Fri, 10 Mar 2017 06:58:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cmJBv-0002AA-2T for qemu-devel@nongnu.org; Fri, 10 Mar 2017 06:58:43 -0500 Received: from mailapp01.imgtec.com ([195.59.15.196]:58243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cmJBu-000296-S8 for qemu-devel@nongnu.org; Fri, 10 Mar 2017 06:58:39 -0500 References: <3d1c16a1-ec05-0367-e569-64a63b34f2e3@redhat.com> <940ff281-82cd-18cf-160e-c5234f65db18@redhat.com> <9d6c61bc-4a95-ce72-3565-e498f9c2b351@redhat.com> <16223ebe-e08d-c686-7ff3-a58db88e3a01@redhat.com> <1aeb7375-d41f-1be4-cbb5-d7bd27801110@redhat.com> <24f60ae4-9a6b-eaa6-7300-1e908eff8a24@redhat.com> From: Yongbok Kim Message-ID: <5913b5db-f3fa-306d-5410-c8b94f1c580c@imgtec.com> Date: Fri, 10 Mar 2017 11:58:31 +0000 MIME-Version: 1.0 In-Reply-To: <24f60ae4-9a6b-eaa6-7300-1e908eff8a24@redhat.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Thomas Huth , Peter Maydell , Jason Wang Cc: Aurelien Jarno , QEMU Developers , Stefan Hajnoczi , Gerd Hoffmann On 10/03/2017 11:53, Thomas Huth wrote: > On 10.03.2017 12:22, Peter Maydell wrote: >> On 10 March 2017 at 12:07, Jason Wang wrote: >>> On 2017=E5=B9=B403=E6=9C=8809=E6=97=A5 18:20, Yongbok Kim wrote: >>>> Indeed but we still use the platform to verify architectural >>>> compatibilities even for newer MIPS architectures. >> >>> I see, but I believe it may need some modifications in the code to su= pport >>> newer architectures? If yes, plan to send them upstream? Since it has= been >>> deprecated, if no new codes it makes sense to deprecate it in qemu to= o. You >>> can still use exist qemu versions to do the verification. >> >> Taking a step back, the reason for deprecating and deleting >> code is to avoid having unmaintained and unused code in QEMU. >> If Yongbok is maintaining the mipssim board and devices >> and is willing to keep them up to spec with current QOM >> and other best practices, and there are test images to >> check they still work, I think that's fine. >=20 > But the Mipssim machine is currently marked as "Orphan" in our > MAINTAINERS file ... Yongbok, if you're still using it, would you maybe > be interested in doing at least "Odd fixes" here? > BTW, I think "F: hw/net/mipsnet.c" should be added to the "Mipssim" > section, too. >=20 > Thomas >=20 Yes I am willing to maintain the machine. I will post a patch to the MAINTAINERS file for the machine and other MIPS machines. Regards, Yongbok