From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] build: introduce target CONFIG_ variables and use them for kvm
Date: Sun, 01 Jul 2012 16:10:45 +0200 [thread overview]
Message-ID: <4FF05A65.6020200@redhat.com> (raw)
In-Reply-To: <4FEDA01B.8010502@suse.de>
Il 29/06/2012 14:31, Andreas Färber ha scritto:
>> > Ping? I can't figure out if this discussion got wedged (in which
>> > case, how should it be unwedged?) or if people were eventually happy
>> > with this patch...
> My guess is we're waiting for Paolo to return from vacation and to
> comment. Basically the patch is "correct" but the open issue is how we
> want to structure the directories - do we want hw/kvm/ to contain
> multiple architectures' files, or do we want to separate devices by
> architecture. There's reasons for both once it works technically.
>
> If Anthony split off the kvm/ change it might be less controversial.
I don't really care much about that, I hope it's temporary anyway. :)
However, one change is necessary: the config-all-devices.mak should also
include the arch defines (or if you don't like the naming, we could have
another config-all-arches.mak file). It should not be hard with grep
(perhaps after renaming the variable should probably be named
CONFIG_ARCH_$ARCH). With this change, the patch is perfectly fine!
Paolo
next prev parent reply other threads:[~2012-07-01 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:44 [Qemu-devel] [PATCH] build: introduce target CONFIG_ variables and use them for kvm Anthony Liguori
2012-06-20 14:51 ` Andreas Färber
2012-06-20 15:01 ` Peter Maydell
2012-06-20 15:04 ` Andreas Färber
2012-06-20 15:07 ` Peter Maydell
2012-06-20 15:23 ` Andreas Färber
2012-06-20 15:20 ` Anthony Liguori
2012-06-20 15:09 ` Peter Maydell
[not found] ` <CAFEAcA-MgQuEfca7bPtUrN-wwN0KVCvXWpcs8Y4tdWL+CbcGFw@mail.gmail.com>
[not found] ` <4FEDA01B.8010502@suse.de>
2012-07-01 14:10 ` Paolo Bonzini [this message]
[not found] ` <4FEDB5F0.1070407@codemonkey.ws>
2012-07-23 14:21 ` Peter Maydell
2012-07-31 17:28 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 12:31 Paolo Bonzini
2012-06-21 13:06 ` Anthony Liguori
2012-06-23 7:53 ` Paolo Bonzini
2012-06-23 10:30 ` Peter Maydell
2012-07-01 13:37 ` Paolo Bonzini
2012-07-01 13:49 ` Peter Maydell
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=4FF05A65.6020200@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=peter.maydell@linaro.org \
--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 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.