From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Samuel Ortiz" <sameo@linux.intel.com>,
haxm-team <haxm-team@intel.com>,
"Claudio Fontana" <cfontana@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH v9 00/10] accel: Allow targets to use Kconfig
Date: Thu, 25 Jun 2020 12:20:17 +0200 [thread overview]
Message-ID: <ee53f6e6-e1dd-2c58-244f-9dc98160e3fd@redhat.com> (raw)
In-Reply-To: <05a17243-6203-0663-2bc1-e5efd59c4e67@redhat.com>
On 25/06/20 09:49, Philippe Mathieu-Daudé wrote:
> Hi Paolo,
>
> Claudio raised an issue with patch #4, so at this point
> I have to admit again having the KVM-only build merged
> for the next release won't be possible :(
>
> Only patch #9 depends on patch #4. Are you OK to take
> the rest of the series, patches 1-3, 5-8, 10 (all but
> 4 and 9). Patches are fully reviewed. If it is easier
> for you I can respin without 4/9.
Yes, sounds good. Patch 4 isn't great and with Meson we can indeed do
better because all config-target.mak files are parsed in a single
non-recursive build.
Paolo
next prev parent reply other threads:[~2020-06-25 10:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 12:33 [PATCH v9 00/10] accel: Allow targets to use Kconfig Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 01/10] MAINTAINERS: Fix KVM path expansion glob Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 02/10] MAINTAINERS: Add an 'overall' entry for accelerators Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 03/10] MAINTAINERS: Cover the HAX accelerator stub Philippe Mathieu-Daudé
2020-06-22 16:47 ` Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 04/10] configure: Generate rule to calculate the base architecture of a target Philippe Mathieu-Daudé
2020-06-19 11:08 ` Philippe Mathieu-Daudé
2020-06-23 8:01 ` Claudio Fontana
2020-06-23 8:45 ` Philippe Mathieu-Daudé
2020-06-23 13:17 ` Philippe Mathieu-Daudé
2020-06-25 8:45 ` Claudio Fontana
2020-06-18 12:33 ` [PATCH v9 05/10] Makefile: Remove dangerous EOL trailing backslash Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 06/10] Makefile: Write MINIKCONF variables as one entry per line Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 07/10] accel/Kconfig: Extract accel selectors into their own config Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 08/10] accel/Kconfig: Add the TCG selector Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 09/10] Makefile: Allow target-specific optional Kconfig Philippe Mathieu-Daudé
2020-06-18 12:33 ` [PATCH v9 10/10] accel/tcg: Add stub for probe_access() Philippe Mathieu-Daudé
2020-06-18 13:28 ` [PATCH v9 00/10] accel: Allow targets to use Kconfig no-reply
2020-06-22 16:47 ` Philippe Mathieu-Daudé
2020-06-25 7:49 ` Philippe Mathieu-Daudé
2020-06-25 10:20 ` Paolo Bonzini [this message]
2020-06-25 10:22 ` Philippe Mathieu-Daudé
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=ee53f6e6-e1dd-2c58-244f-9dc98160e3fd@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=haxm-team@intel.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sameo@linux.intel.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).