|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH] Permit zero-sized qemu_malloc() & friends |
Date: | Mon, 07 Dec 2009 21:01:05 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091203 Fedora/3.0-3.13.rc2.fc12 Thunderbird/3.0 |
On 12/07/2009 08:59 PM, Anthony Liguori wrote:
Avi Kivity wrote:My problem is with stable-0.12. Consider upstream fixed. 1) Bug reported against qemu-0.12.0.2) Developer writes patch against master, submits, all is well except for the CODING_STYLE argument it triggers. 3) Developer writes patch against stable-0.12, can't test because testing crashes in some place where production doesn't crash.Stable-0.12 always carries a VERSION of 0.12.x where x < 50. This means that the stable-0.12 branch will always behave like a production release.You don't get -Werror on stable-0.XX and you won't get zero malloc()s assert.
That's good enough for me. Allow 0 for 0.12 and new allocation functions for mainline, then?
-- Do not meddle in the internals of kernels, for they are subtle and quick to panic.
[Prev in Thread] | Current Thread | [Next in Thread] |