qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	f4bug@armsat.org, QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v1 1/2] hw/tricore: fix inclusion of tricore_testboard
Date: Tue, 20 Jul 2021 10:46:08 +0100	[thread overview]
Message-ID: <87zguhmi4p.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8VGYTc2jrdB+ET4xFODDv0SniTjnUAYr+4dgjSZEsmiA@mail.gmail.com>


Peter Maydell <peter.maydell@linaro.org> writes:

> On Mon, 19 Jul 2021 at 20:52, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> We inadvertently added a symbol clash causing the build not to include
>> the testboard needed for check-tcg.
>>
>> Fixes: f4063f9c31 ("meson: Introduce target-specific Kconfig")
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>>  configs/devices/tricore-softmmu/default.mak | 1 +
>>  hw/tricore/Kconfig                          | 3 +--
>>  hw/tricore/meson.build                      | 4 ++--
>>  3 files changed, 4 insertions(+), 4 deletions(-)
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> as far as this fix goes (though maybe CONFIG_TRICORE_TESTBOARD would be better?)
>
> But I still don't understand and would like to know:
> (1) why doesn't CONFIG_TRICORE get set by Kconfig anyway, as
> f4063f9c31 claims to be doing?

It does (or should) thanks to meson:

  'CONFIG_' + config_target['TARGET_ARCH'].to_upper() + '=y'

> (2) what are the CONFIG_$ARCH flags for? Apart from this, we
> don't seem to be using any of them, as demonstrated by the fact
> that nothing else broke :-)

They need to be declared in Kconfig otherwise minikconf complains about
them not being defined when you pass it in. This is part of minikconf's
sanity checking code.

>
> thanks
> -- PMM


-- 
Alex Bennée


  reply	other threads:[~2021-07-20  9:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 19:50 [PATCH for 6.1 v1 0/2] tricore fixes Alex Bennée
2021-07-19 19:50 ` [PATCH v1 1/2] hw/tricore: fix inclusion of tricore_testboard Alex Bennée
2021-07-19 21:21   ` Peter Maydell
2021-07-20  9:46     ` Alex Bennée [this message]
2021-07-20  9:52       ` Peter Maydell
2021-07-20 10:35         ` Alex Bennée
2021-07-20 11:00           ` Alex Bennée
2021-07-19 23:09   ` Philippe Mathieu-Daudé
2021-07-19 19:50 ` [PATCH v1 2/2] gitlab: enable a very minimal build with the tricore container Alex Bennée
2021-07-19 21:36   ` Alex Bennée

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=87zguhmi4p.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=f4bug@armsat.org \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=pbonzini@redhat.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 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).