From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44477) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5oP9-0003dn-3L for qemu-devel@nongnu.org; Fri, 19 Jun 2015 00:59:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5oP5-0000s9-0v for qemu-devel@nongnu.org; Fri, 19 Jun 2015 00:59:51 -0400 Received: from icp-osb-irony-out8.external.iinet.net.au ([203.59.1.225]:31653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5oP4-0000nH-KX for qemu-devel@nongnu.org; Fri, 19 Jun 2015 00:59:46 -0400 Message-ID: <5583A1E3.302@uclinux.org> Date: Fri, 19 Jun 2015 15:00:19 +1000 From: Greg Ungerer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] m68k orphaned? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi All, I see in the MAINTAINERS file that pretty much everything related to the m68k architecture is listed as "Orphan". I have some patches that have been around for quite a while (posted here twice) to fix some issues with the ColdFire support. [See https://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg03224.html] They are still relevant, still apply, and are still needed. Does anyone have any suggestions how I can get them pushed into mainline qemu? Regards Greg