From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42833) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bz5nZ-0004lD-5Y for qemu-devel@nongnu.org; Tue, 25 Oct 2016 13:46:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bz5nD-0004XN-Hb for qemu-devel@nongnu.org; Tue, 25 Oct 2016 13:46:05 -0400 Received: from mail-qt0-x232.google.com ([2607:f8b0:400d:c0d::232]:35548) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bz5nC-0004Ws-R6 for qemu-devel@nongnu.org; Tue, 25 Oct 2016 13:45:43 -0400 Received: by mail-qt0-x232.google.com with SMTP id g32so10182863qta.2 for ; Tue, 25 Oct 2016 10:45:42 -0700 (PDT) Sender: Richard Henderson References: <1477407021-30755-1-git-send-email-laurent@vivier.eu> From: Richard Henderson Message-ID: <1f16fcc8-6f78-fa37-f58a-14af3981429a@twiddle.net> Date: Tue, 25 Oct 2016 10:45:39 -0700 MIME-Version: 1.0 In-Reply-To: <1477407021-30755-1-git-send-email-laurent@vivier.eu> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/23] target-m68k: prepare to introduce 680x0 instruction set List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laurent Vivier , qemu-devel@nongnu.org Cc: schwab@linux-m68k.org, agraf@suse.de, gerg@uclinux.org, Peter Maydell On 10/25/2016 07:49 AM, Laurent Vivier wrote: > As I'm not able to manage too large series, > this series is a subset of the series I sent in May: > https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg00501.html We're fond of smaller series too. ;-) > > It doesn't introduce any new instructions but: > - introduce the new processors feature flags > - introduce new flags management as proposed by Richard > > I've checked it doesn't break coldfire support: > http://wiki.qemu.org/download/coldfire-test-0.1.tar.bz2 > but it can't boot a 680x0 processor kernel. > > I've fixed some style issues reported by checkpatch.pl and merged > some of the patches cleaning up flags (as suggested by Richard). It looks as if I've reviewed everything in here already. I'm perfectly happy for this to be merged now. Do you have a gpg key with signatures valid for Peter to do a signed pull? Otherwise, Peter, are you happy to merge this by hand or should I create a branch from which you can pull? r~