From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] kqemu: only compile kqemu.o if actually needed
Date: Sat, 18 Apr 2009 22:26:38 +0300 [thread overview]
Message-ID: <f43fc5580904181226n194581b0l317f035e706d7b96@mail.gmail.com> (raw)
In-Reply-To: <1240055669.12170.20.camel@localhost.localdomain>
On 4/18/09, Paul Bolle <pebolle@tiscali.nl> wrote:
> kqemu.o is compiled even if kqemu support is disabled. This is useless
> (kqemu.o should provide nothing that is actually used in that case) and
> slightly confusing. So introduce CONFIG_KQEMU for optionally compiling
> kqemu.o.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> If this is accepted a next step could be to merge CONFIG_KQEMU and
> USE_KQEMU.
Thanks, applied. Merging those would be great.
next prev parent reply other threads:[~2009-04-18 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 11:54 [Qemu-devel] [PATCH] kqemu: only compile kqemu.o if actually needed Paul Bolle
2009-04-18 19:26 ` Blue Swirl [this message]
2009-04-18 21:51 ` [Qemu-devel] [PATCH] kqemu: merge CONFIG_KQEMU and USE_KQEMU Paul Bolle
2009-04-19 10:18 ` [Qemu-devel] " Blue Swirl
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=f43fc5580904181226n194581b0l317f035e706d7b96@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 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).