From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51222)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1X7lR1-0003qG-O5
	for qemu-devel@nongnu.org; Thu, 17 Jul 2014 09:09:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1X7lQs-0003Rx-Np
	for qemu-devel@nongnu.org; Thu, 17 Jul 2014 09:09:19 -0400
Received: from [2001:41d0:8:2b42::1] (port=48480 helo=greensocs.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1X7lQs-0003RH-ID
	for qemu-devel@nongnu.org; Thu, 17 Jul 2014 09:09:10 -0400
Message-ID: <53C7CAF2.60903@greensocs.com>
Date: Thu, 17 Jul 2014 15:09:06 +0200
From: Frederic Konrad <fred.konrad@greensocs.com>
MIME-Version: 1.0
References: <CAFEAcA-D24Dy0M1msberD_Od1ObvFb=ZEUJhDWHhFW6ZDjmkwQ@mail.gmail.com>
In-Reply-To: <CAFEAcA-D24Dy0M1msberD_Od1ObvFb=ZEUJhDWHhFW6ZDjmkwQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] status for rc3/release
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>, QEMU Developers <qemu-devel@nongnu.org>

On 17/07/2014 11:45, Peter Maydell wrote:
> So we just released rc2. The proposed schedule has
> rc3 next Tuesday, with final release the Tuesday after.
>
> My thought is that we should aim for rc3 to add only
> a fairly small number of focussed and "safe" bugfixes,
> with the intention of making the final release be the
> same as rc3 if no showstopper bugs are discovered.
> If there are any showstoppers in rc3 we have a week
> to fix them and roll and test an rc4.
>
> Does it seem to other people like we're on track for that?
> I don't do the level of testing that I think Anthony had
> access to, so I'm reliant on those of you doing testing
> of the rc tarballs to report problems...
>
> thanks
> -- PMM
>
Hi,

Is it possible to include the "cadence_uart: check serial backend before 
using it."
bug fix.

I think it's relatively safe.

Thanks,
Fred