From: Alistair Francis <alistair23@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-arm <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Alistair Francis <alistair@alistair23.me>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] hw/intc: Only build the xlnx-iomod-intc device for the MicroBlaze PMU
Date: Mon, 29 Apr 2019 10:29:28 -0700 [thread overview]
Message-ID: <CAKmqyKMMTQtq2sxSH85oPzsK-vVX1jELaQALPhAEJ6EpTSD66g@mail.gmail.com> (raw)
In-Reply-To: <20190427141459.19728-3-philmd@redhat.com>
On Sat, Apr 27, 2019 at 7:17 AM Philippe Mathieu-Daudé
<philmd@redhat.com> wrote:
>
> The Xilinx I/O Module Interrupt Controller is only used by the
> MicroBlaze PMU, not by the AArch64 machine.
> Move it from the generic ZynqMP object list to the PMU specific.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
> ---
> hw/intc/Makefile.objs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/intc/Makefile.objs b/hw/intc/Makefile.objs
> index df712c3e6c9..247e8016cb8 100644
> --- a/hw/intc/Makefile.objs
> +++ b/hw/intc/Makefile.objs
> @@ -3,7 +3,7 @@ common-obj-$(CONFIG_I8259) += i8259_common.o i8259.o
> common-obj-$(CONFIG_PL190) += pl190.o
> common-obj-$(CONFIG_PUV3) += puv3_intc.o
> common-obj-$(CONFIG_XILINX) += xilinx_intc.o
> -common-obj-$(CONFIG_XLNX_ZYNQMP) += xlnx-pmu-iomod-intc.o
> +common-obj-$(CONFIG_XLNX_ZYNQMP_PMU) += xlnx-pmu-iomod-intc.o
> common-obj-$(CONFIG_XLNX_ZYNQMP) += xlnx-zynqmp-ipi.o
> common-obj-$(CONFIG_ETRAXFS) += etraxfs_pic.o
> common-obj-$(CONFIG_IMX) += imx_avic.o imx_gpcv2.o
> --
> 2.20.1
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Francis <alistair23@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Alistair Francis <alistair@alistair23.me>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] hw/intc: Only build the xlnx-iomod-intc device for the MicroBlaze PMU
Date: Mon, 29 Apr 2019 10:29:28 -0700 [thread overview]
Message-ID: <CAKmqyKMMTQtq2sxSH85oPzsK-vVX1jELaQALPhAEJ6EpTSD66g@mail.gmail.com> (raw)
Message-ID: <20190429172928.PA5mGANdijq_2yZqPlU0GICPe-ycoCvZ7_sOHgwS-J8@z> (raw)
In-Reply-To: <20190427141459.19728-3-philmd@redhat.com>
On Sat, Apr 27, 2019 at 7:17 AM Philippe Mathieu-Daudé
<philmd@redhat.com> wrote:
>
> The Xilinx I/O Module Interrupt Controller is only used by the
> MicroBlaze PMU, not by the AArch64 machine.
> Move it from the generic ZynqMP object list to the PMU specific.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
> ---
> hw/intc/Makefile.objs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/intc/Makefile.objs b/hw/intc/Makefile.objs
> index df712c3e6c9..247e8016cb8 100644
> --- a/hw/intc/Makefile.objs
> +++ b/hw/intc/Makefile.objs
> @@ -3,7 +3,7 @@ common-obj-$(CONFIG_I8259) += i8259_common.o i8259.o
> common-obj-$(CONFIG_PL190) += pl190.o
> common-obj-$(CONFIG_PUV3) += puv3_intc.o
> common-obj-$(CONFIG_XILINX) += xilinx_intc.o
> -common-obj-$(CONFIG_XLNX_ZYNQMP) += xlnx-pmu-iomod-intc.o
> +common-obj-$(CONFIG_XLNX_ZYNQMP_PMU) += xlnx-pmu-iomod-intc.o
> common-obj-$(CONFIG_XLNX_ZYNQMP) += xlnx-zynqmp-ipi.o
> common-obj-$(CONFIG_ETRAXFS) += etraxfs_pic.o
> common-obj-$(CONFIG_IMX) += imx_avic.o imx_gpcv2.o
> --
> 2.20.1
>
>
next prev parent reply other threads:[~2019-04-29 17:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 14:14 [Qemu-devel] [PATCH 0/3] hw/microblaze: Kconfig cleanup Philippe Mathieu-Daudé
2019-04-27 14:14 ` Philippe Mathieu-Daudé
2019-04-27 14:14 ` [Qemu-devel] [PATCH 1/3] hw/Kconfig: Move the generic XLNX_ZYNQMP to the root hw/Kconfig Philippe Mathieu-Daudé
2019-04-27 14:14 ` Philippe Mathieu-Daudé
2019-04-29 17:28 ` Alistair Francis
2019-04-29 17:28 ` Alistair Francis
2019-04-27 14:14 ` [Qemu-devel] [PATCH 2/3] hw/intc: Only build the xlnx-iomod-intc device for the MicroBlaze PMU Philippe Mathieu-Daudé
2019-04-27 14:14 ` Philippe Mathieu-Daudé
2019-04-27 14:43 ` Thomas Huth
2019-04-27 14:43 ` Thomas Huth
2019-04-29 17:29 ` Alistair Francis [this message]
2019-04-29 17:29 ` Alistair Francis
2019-04-27 14:14 ` [Qemu-devel] [PATCH 3/3] hw/dma: Do not build the xlnx_dpdma device for the MicroBlaze machines Philippe Mathieu-Daudé
2019-04-27 14:14 ` Philippe Mathieu-Daudé
2019-04-27 14:46 ` Thomas Huth
2019-04-27 14:46 ` Thomas Huth
2019-05-02 9:12 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-05-02 9:12 ` Laurent Vivier
2019-04-29 17:30 ` [Qemu-devel] " Alistair Francis
2019-04-29 17:30 ` Alistair Francis
2019-04-30 19:55 ` [Qemu-devel] [PATCH 0/3] hw/microblaze: Kconfig cleanup Paolo Bonzini
2019-04-30 19:55 ` Paolo Bonzini
2019-05-27 16:10 ` Philippe Mathieu-Daudé
2019-05-27 18:43 ` Paolo Bonzini
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=CAKmqyKMMTQtq2sxSH85oPzsK-vVX1jELaQALPhAEJ6EpTSD66g@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).