public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm list <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>, Kenni Lund <kenni@kelu.dk>
Subject: Re: qemu-kvm.git stable requests
Date: Thu, 01 Apr 2010 18:25:58 +0300	[thread overview]
Message-ID: <4BB4BB06.8080506@redhat.com> (raw)
In-Reply-To: <B15218F5-50E4-4151-8EA2-624809D5DD22@suse.de>

On 03/31/2010 11:26 AM, Alexander Graf wrote:
> Howdy,
>
> Apparently there was just the very first case of someone requiring my patch to enable BAR regions<  4k. To enable people to use those devices with a released version, I'd suggest cherry-picking these commits into 0.12-stable:
>
> commit 8845b72377a42443b249360b9cd3d6f1e8cfb097
> Author: Alexander Graf<agraf@suse.de>
> Date:   Thu Dec 17 16:04:44 2009 +0100
>
> commit be5a9efb3359cac07217d477b44f6bd0e17658f0
> Author: Michael S. Tsirkin<mst@redhat.com>
> Date:   Wed Dec 23 12:07:47 2009 +0200
>    

These look reasonable (but please include the subject line in the future).

> While at it, I realized that the friendly help output if a device is currently in use by a driver is not available. So I'd also suggest taking those in to -stable:
>
>
> commit 0cbd39044aa9f6c4462b7783376c894786f8de77
> Author: Alexander Graf<agraf@suse.de>
> Date:   Thu Dec 17 16:04:45 2009 +0100
>
> commit 27a3fa20f302e64fe10d5c2f0f5c73d73e336166
> Author: Alexander Graf<agraf@suse.de>
> Date:   Thu Dec 17 16:04:46 2009 +0100
>
>    

I don't think it's worth the risk of a regression.  One one hand, 
unfriendly help output.  On the other hand, things break, data 
corruption, end of the world.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-04-01 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  8:26 qemu-kvm.git stable requests Alexander Graf
2010-04-01 15:25 ` Avi Kivity [this message]
2010-04-05 19:18   ` Marcelo Tosatti

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=4BB4BB06.8080506@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kenni@kelu.dk \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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