qemu-trivial.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH 2/4] hw/core: Add a config switch for the "or-irq" device
Date: Tue, 14 May 2019 12:40:32 +0200	[thread overview]
Message-ID: <6b38c9ea-e022-eac8-d19f-39f17956da49@redhat.com> (raw)
In-Reply-To: <aabf08dd-0c9f-63dd-1c49-f31f6c150392@redhat.com>

On 14/05/2019 12.35, Philippe Mathieu-Daudé wrote:
> On 5/14/19 12:00 PM, Thomas Huth wrote:
>> The "or-irq" device is only used by certain machines. Let's add
>> a proper config switch for it so that it only gets compiled when we
>> really need it.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>  hw/arm/Kconfig        | 2 ++
>>  hw/core/Kconfig       | 3 +++
>>  hw/core/Makefile.objs | 2 +-
>>  hw/pci-host/Kconfig   | 3 ++-
>>  4 files changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
>> index af8cffde9c..0bb3bbe9d3 100644
>> --- a/hw/arm/Kconfig
>> +++ b/hw/arm/Kconfig
>> @@ -277,6 +277,7 @@ config RASPI
>>  config STM32F205_SOC
>>      bool
>>      select ARM_V7M
>> +    select OR_IRQ
>>      select STM32F2XX_TIMER
>>      select STM32F2XX_USART
>>      select STM32F2XX_SYSCFG
>> @@ -424,6 +425,7 @@ config ARMSSE
>>      select IOTKIT_SECCTL
>>      select IOTKIT_SYSCTL
>>      select IOTKIT_SYSINFO
>> +    select OR_IRQ
>>      select TZ_MPC
>>      select TZ_MSC
>>      select TZ_PPC
> 
> You missed the MPS2* boards

No, the MPS2 boards "select ARMSSE", so this gets added via the above
hunk there. But as mentioned in the reply to Peter, it's likely better
to add it there, too.

 Thomas


  reply	other threads:[~2019-05-14 10:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 10:00 [Qemu-trivial] [PATCH 0/4] Kconfig switches for core / misc devices Thomas Huth
2019-05-14 10:00 ` [Qemu-trivial] [PATCH 1/4] hw/core: Add a config switch for the "register" device Thomas Huth
2019-05-14 10:31   ` Philippe Mathieu-Daudé
2019-05-14 10:38     ` Thomas Huth
2019-05-22 14:24       ` [Qemu-trivial] [Qemu-devel] " Thomas Huth
2019-05-14 10:00 ` [Qemu-trivial] [PATCH 2/4] hw/core: Add a config switch for the "or-irq" device Thomas Huth
2019-05-14 10:06   ` [Qemu-trivial] [Qemu-arm] " Peter Maydell
2019-05-14 10:25     ` Philippe Mathieu-Daudé
2019-05-14 10:36       ` Thomas Huth
2019-05-14 10:40       ` Philippe Mathieu-Daudé
2019-05-14 10:35   ` [Qemu-trivial] " Philippe Mathieu-Daudé
2019-05-14 10:40     ` Thomas Huth [this message]
2019-05-14 10:00 ` [Qemu-trivial] [PATCH 3/4] hw/core: Add a config switch for the "split-irq" device Thomas Huth
2019-05-14 10:00 ` [Qemu-trivial] [PATCH 4/4] hw/misc: Add a config switch for the "unimplemented" device Thomas Huth
2019-05-14 10:08   ` [Qemu-trivial] [Qemu-arm] " Peter Maydell
2019-05-14 10:43     ` Thomas Huth
2019-05-14 10:07 ` [Qemu-trivial] [PATCH 0/4] Kconfig switches for core / misc devices 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=6b38c9ea-e022-eac8-d19f-39f17956da49@redhat.com \
    --to=thuth@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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).