From: Paolo Bonzini <pbonzini@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Yuri Pudgorodskiy <yur@virtuozzo.com>,
Roman Kagan <rkagan@virtuozzo.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects
Date: Mon, 14 Dec 2015 10:52:38 +0100 [thread overview]
Message-ID: <566E9166.4060101@redhat.com> (raw)
In-Reply-To: <566E90B5.3080203@openvz.org>
On 14/12/2015 10:49, Denis V. Lunev wrote:
>>
>> In any case, even if this is a bug that we want to add to 2.5.1, it's
>> definitely too late for 2.5---at any time after soft freeze.
> ok. 2.5.1 would be really great. Thank you for a prompt reply.
>
> Though I have a question about the freeze policy as
> other people still accepting user-visible bugfixes
> after a soft freeze.
Of course things are up to the individual maintainer but, in general, I
think that guest-visible changes should be vetted very carefully after
soft freeze.
It depends on the effect of the change. Changing ACPI tables is quite
more far reaching than, say, fixing an infinite loop in a device model
(which has never been triggered so far, or we would have had a bug
reported).
Paolo
next prev parent reply other threads:[~2015-12-14 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 8:22 [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects Denis V. Lunev
2015-12-14 9:21 ` Michael S. Tsirkin
2015-12-14 9:26 ` Denis V. Lunev
2015-12-14 9:28 ` Paolo Bonzini
2015-12-14 9:41 ` Denis V. Lunev
2015-12-14 9:44 ` Paolo Bonzini
2015-12-14 9:49 ` Denis V. Lunev
2015-12-14 9:52 ` Paolo Bonzini [this message]
2015-12-14 14:21 ` Michael S. Tsirkin
2015-12-14 15:05 ` Igor Mammedov
2015-12-14 15:11 ` Denis V. Lunev
2015-12-14 15:27 ` Igor Mammedov
2015-12-14 15:38 ` Roman Kagan
2015-12-14 15:59 ` Igor Mammedov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566E9166.4060101@redhat.com \
--to=pbonzini@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
--cc=yur@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).