public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: kvm-kmod.git
Date: Tue, 28 Apr 2009 14:00:43 +0300	[thread overview]
Message-ID: <49F6E1DB.5000103@redhat.com> (raw)
In-Reply-To: <20090428105333.GA27513@redhat.com>

Michael S. Tsirkin wrote:
> On Tue, Apr 28, 2009 at 01:53:26PM +0300, Avi Kivity wrote:
>   
>> Michael S. Tsirkin wrote:
>>     
>>>> Or maybe, add a s/CONFIG_KVM_TRACE/CONFIG_KMOD_KVM_TRACE/ to make the 
>>>>  two options independent.
>>>>     
>>>>         
>>> You decide. 
>>>       
>> Well, I think it's less confusing.
>>     
>
> Fine. Patch?
>
>   

Please.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2009-04-28 11:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 12:32 kvm-kmod.git Avi Kivity
2009-04-27 14:08 ` kvm-kmod.git Farkas Levente
2009-04-27 14:56   ` kvm-kmod.git Avi Kivity
2009-04-27 17:18 ` kvm-kmod.git Cam Macdonell
2009-04-28  6:39   ` kvm-kmod.git Avi Kivity
2009-04-28 10:20 ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 10:24   ` kvm-kmod.git Avi Kivity
2009-04-28 10:34     ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 10:53       ` kvm-kmod.git Avi Kivity
2009-04-28 10:53         ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 11:00           ` Avi Kivity [this message]
2009-06-01 16:53         ` kvm-kmod.git Ryan Harper
2009-06-01 17:01           ` kvm-kmod.git Avi Kivity
2009-06-01 18:00             ` kvm-kmod.git Ryan Harper
2009-06-01 18:17               ` kvm-kmod.git Avi Kivity
2009-06-01 18:15             ` kvm-kmod.git Ryan Harper
2009-06-01 18:19               ` kvm-kmod.git Avi Kivity
2009-06-01 18:47                 ` kvm-kmod.git Ryan Harper
2009-06-01 19:40                   ` kvm-kmod.git Avi Kivity

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=49F6E1DB.5000103@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@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