From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58679) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUZlk-00047T-Cc for qemu-devel@nongnu.org; Mon, 31 Mar 2014 06:48:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WUZle-00028g-5C for qemu-devel@nongnu.org; Mon, 31 Mar 2014 06:48:44 -0400 Received: from mail-pb0-f44.google.com ([209.85.160.44]:49476) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUZld-00028Y-VR for qemu-devel@nongnu.org; Mon, 31 Mar 2014 06:48:38 -0400 Received: by mail-pb0-f44.google.com with SMTP id rp16so8064788pbb.3 for ; Mon, 31 Mar 2014 03:48:37 -0700 (PDT) Message-ID: <533947FE.2060106@ozlabs.ru> Date: Mon, 31 Mar 2014 21:48:30 +1100 From: Alexey Kardashevskiy MIME-Version: 1.0 References: <1395491149-21432-1-git-send-email-aik@ozlabs.ru> <20140322144303.GA31470@zubnet.me.uk> <532FCFA3.3040804@ozlabs.ru> <5338C407.7020104@ozlabs.ru> <53392634.3090602@suse.de> <53392C61.3050007@ozlabs.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH v2] target-ppc: improve "info registers" by printing SPRs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Alexander Graf , Fabien Chouteau , QEMU Developers , Stuart Brady , "qemu-ppc@nongnu.org" , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= On 03/31/2014 09:07 PM, Peter Maydell wrote: > On 31 March 2014 09:50, Alexey Kardashevskiy wrote: >> On 03/31/2014 07:24 PM, Andreas Färber wrote: >>> Am 31.03.2014 03:25, schrieb Alexey Kardashevskiy: >>>> Noone has an opinion? Come on! :) >>> >>> We're in Hard Freeze!!! >:-| There's more important works than post-2.0 >>> debug infos ATM. Anyway... >> >> >> Are you saying I should not be posting anything which is not "for 2.0" >> until it is released? Oookay. > > There's nothing wrong with posting patchsets that are targeting > post-2.0 now. Andreas' point is that you can't necessarily expect > review of them before release, because the people whose code > review you might want are likely to be busy with things which > are release-relevant, and so for some of those people post-2.0 > things will go on the "look at later" queue. I rather wanted Stuart and Fabien to comment, sorry for misunderstanding. -- Alexey