From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH 0/2] add flags for conditional compilation of qemu dependencies
Date: Wed, 17 Oct 2007 18:55:02 +0200 [thread overview]
Message-ID: <47163E66.5010501@qumranet.com> (raw)
In-Reply-To: <20071017161133.GB27102@tapir>
Carlo Marcelo Arenas Belon wrote:
> This series adds options to kvm's configure that match the ones used by qemu
> to conditionally enable or disable options that alter its runtime dependencies
> and functionality, like for example, support for alsa or TLS encrypted vnc
> sessions.
>
>
Applied both, thanks. But if someone is thinking of a patch flood to
add all qemu options, I'd prefer a passthrough instead.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-17 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 16:11 [PATCH 0/2] add flags for conditional compilation of qemu dependencies Carlo Marcelo Arenas Belon
2007-10-17 16:14 ` [PATCH 1/2] alsa configure option Carlo Marcelo Arenas Belon
2007-10-17 16:16 ` [PATCH 2/2] vnc-tls configure flag Carlo Marcelo Arenas Belon
2007-10-17 16:55 ` Avi Kivity [this message]
[not found] ` <47163E66.5010501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-18 18:04 ` [PATCH 0/2] add flags for conditional compilation of qemu dependencies Carlo Marcelo Arenas Belon
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=47163E66.5010501@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.