From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/3] configure: add missing CONFIG_FOO variables
Date: Mon, 14 Sep 2020 12:50:23 +0200 [thread overview]
Message-ID: <8cda7b10-1eba-ccfe-1cae-c023fba87553@redhat.com> (raw)
In-Reply-To: <20200914095231.621068-1-stefanha@redhat.com>
On 14/09/20 11:52, Stefan Hajnoczi wrote:
> The meson.build feature summary checks the presence of CONFIG_FOO variables.
> Several of these variables are never emitted by ./configure so the feature
> summary always shows these features as disabled.
>
> Stefan Hajnoczi (3):
> configure: add missing CONFIG_TCMALLOC
> configure: add missing CONFIG_JEMALLOC
> configure: rename QEMU_GA_MSI_ENABLED to CONFIG_QGA_MSI
>
> configure | 10 +++++++++-
> Makefile | 2 +-
> meson.build | 2 +-
> 3 files changed, 11 insertions(+), 3 deletions(-)
>
Thanks!
For 1 and 2 I think it's simpler to move the whole test to Meson. I
already have a patch for that, though I was going to send it next week.
Paolo
next prev parent reply other threads:[~2020-09-14 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:52 [PATCH 0/3] configure: add missing CONFIG_FOO variables Stefan Hajnoczi
2020-09-14 9:52 ` [PATCH 1/3] configure: add missing CONFIG_TCMALLOC Stefan Hajnoczi
2020-09-14 9:52 ` [PATCH 2/3] configure: add missing CONFIG_JEMALLOC Stefan Hajnoczi
2020-09-14 9:52 ` [PATCH 3/3] configure: rename QEMU_GA_MSI_ENABLED to CONFIG_QGA_MSI Stefan Hajnoczi
2020-09-14 10:50 ` Paolo Bonzini [this message]
2020-09-15 10:56 ` [PATCH 0/3] configure: add missing CONFIG_FOO variables Stefan Hajnoczi
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=8cda7b10-1eba-ccfe-1cae-c023fba87553@redhat.com \
--to=pbonzini@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).