From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alistair Francis" <alistair.francis@xilinx.com>,
qemu-ppc <qemu-ppc@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH 1/5] configs: Add a CONFIG_OR_IRQ switch for the or-irq device
Date: Fri, 19 Oct 2018 14:58:42 +0100 [thread overview]
Message-ID: <CAFEAcA8EzuwgobawU3KhCcHRyMWG=5d2pZ5KSe0rHeRkUteU9Q@mail.gmail.com> (raw)
In-Reply-To: <1539954845-26716-2-git-send-email-thuth@redhat.com>
On 19 October 2018 at 14:14, Thomas Huth <thuth@redhat.com> wrote:
> If the user only wants to compile targets that do not require the
> "or-irq" device, we should also not compile or-irq.c. Add a proper
> CONFIG_OR_IRQ switch to be able to choose this more flexibly.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> default-configs/arm-softmmu.mak | 1 +
> default-configs/ppc-softmmu.mak | 1 +
> hw/core/Makefile.objs | 2 +-
> 3 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/default-configs/arm-softmmu.mak b/default-configs/arm-softmmu.mak
> index 2420491..dc6a581 100644
> --- a/default-configs/arm-softmmu.mak
> +++ b/default-configs/arm-softmmu.mak
> @@ -4,6 +4,7 @@ include pci.mak
> include usb.mak
> CONFIG_VGA=y
> CONFIG_NAND=y
> +CONFIG_OR_IRQ=y
> CONFIG_ECC=y
> CONFIG_SERIAL=y
> CONFIG_SERIAL_ISA=y
> diff --git a/default-configs/ppc-softmmu.mak b/default-configs/ppc-softmmu.mak
> index 3181bbf..83235af 100644
> --- a/default-configs/ppc-softmmu.mak
> +++ b/default-configs/ppc-softmmu.mak
> @@ -68,3 +68,4 @@ CONFIG_PC87312=y
> CONFIG_PCSPK=y
> CONFIG_IDE_ISA=y
> CONFIG_CS4231A=y
> +CONFIG_OR_IRQ=y
Again, this is generic. We shouldn't need to mess with default-configs
files if we use it in some other architecture.
thanks
-- PMM
next prev parent reply other threads:[~2018-10-19 13:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 13:14 [Qemu-devel] [PATCH 0/5] Add more CONFIG switches to make the build more modular Thomas Huth
2018-10-19 13:14 ` [Qemu-devel] [PATCH 1/5] configs: Add a CONFIG_OR_IRQ switch for the or-irq device Thomas Huth
2018-10-19 13:58 ` Peter Maydell [this message]
2018-10-19 13:14 ` [Qemu-devel] [PATCH 2/5] configs: Add a CONFIG_SPLIT_IRQ switch for the split-irq device Thomas Huth
2018-10-19 14:44 ` Peter Maydell
2018-10-19 13:14 ` [Qemu-devel] [PATCH 3/5] configs: Add a CONFIG_REGISTER switch for the "register" device Thomas Huth
2018-10-19 14:44 ` Peter Maydell
2018-10-19 13:14 ` [Qemu-devel] [PATCH 4/5] configs: Add a CONFIG_UNIMP switch for the "unimplemented-device" Thomas Huth
2018-10-19 13:57 ` Peter Maydell
2018-10-19 14:40 ` Thomas Huth
2018-10-19 14:43 ` Peter Maydell
2018-10-19 15:59 ` Paolo Bonzini
2018-10-19 16:25 ` Philippe Mathieu-Daudé
2018-10-19 16:44 ` Paolo Bonzini
2018-10-19 16:54 ` Peter Maydell
2018-10-20 19:57 ` Paolo Bonzini
2018-10-19 13:14 ` [Qemu-devel] [PATCH 5/5] configs: Add a CONFIG_SMC37C669 switch for the "smc37c669-superio" device Thomas Huth
2018-10-19 14:46 ` Peter Maydell
2018-10-19 16:35 ` Philippe Mathieu-Daudé
2018-10-19 16:38 ` 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='CAFEAcA8EzuwgobawU3KhCcHRyMWG=5d2pZ5KSe0rHeRkUteU9Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@xilinx.com \
--cc=edgar.iglesias@xilinx.com \
--cc=f4bug@amsat.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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).