From: "Murilo Opsfelder Araújo" <muriloo@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-ppc@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
mopsfelder@gmail.com,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Fabiano Rosas" <farosas@linux.ibm.com>
Subject: Re: [PATCH v2] mos6522: fix linking error when CONFIG_MOS6522 is not set
Date: Tue, 10 May 2022 21:01:44 -0300 [thread overview]
Message-ID: <d0fa9d1f-bc09-5068-b222-f94cc5bc7810@linux.ibm.com> (raw)
In-Reply-To: <358f4e05-a29f-6e2f-5fc3-1df6c2b8315c@redhat.com>
Hi, Thomas.
On 5/10/22 04:24, Thomas Huth wrote:
> On 06/05/2022 03.16, Murilo Opsfelder Araujo wrote:
>> When CONFIG_MOS6522 is not set, building ppc64-softmmu target fails:
>>
>> /usr/bin/ld: libqemu-ppc64-softmmu.fa.p/monitor_misc.c.o:(.data+0x1158): undefined reference to `hmp_info_via'
>>
>> Make devices configuration available in hmp-commands*.hx and check for
>> CONFIG_MOS6522.
>>
>> Fixes: 409e9f7131e5 (mos6522: add "info via" HMP command for debugging)
>> Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
>> Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>> Cc: Fabiano Rosas <farosas@linux.ibm.com>
>> ---
>> v2:
>> - Included devices configuration in monitor/misc.c
>>
>> v1:
>> - https://lore.kernel.org/qemu-devel/20220429233146.29662-1-muriloo@linux.ibm.com/
>>
>> hmp-commands-info.hx | 2 ++
>> monitor/misc.c | 3 +++
>> 2 files changed, 5 insertions(+)
>>
>> diff --git a/hmp-commands-info.hx b/hmp-commands-info.hx
>> index adfa085a9b..9ad784dd9f 100644
>> --- a/hmp-commands-info.hx
>> +++ b/hmp-commands-info.hx
>> @@ -881,6 +881,7 @@ SRST
>> ERST
>> #if defined(TARGET_M68K) || defined(TARGET_PPC)
>> +#if defined(CONFIG_MOS6522)
>
> I think you could even get rid of the TARGET_ stuff now that the CONFIG line works!
>
>> {
>> .name = "via",
>> .args_type = "",
>> @@ -889,6 +890,7 @@ ERST
>> .cmd = hmp_info_via,
>> },
>> #endif
>> +#endif
>> SRST
>> ``info via``
>> diff --git a/monitor/misc.c b/monitor/misc.c
>> index 6c5bb82d3b..3d2312ba8d 100644
>> --- a/monitor/misc.c
>> +++ b/monitor/misc.c
>> @@ -84,6 +84,9 @@
>> #include "hw/s390x/storage-attributes.h"
>> #endif
>> +/* Make devices configuration available for use in hmp-commands*.hx templates */
>> +#include CONFIG_DEVICES
>
> Looks reasonable to me.
>
> So with the "#if defined(TARGET_M68K) || defined(TARGET_PPC)" removed:
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
I've sent v3 with your suggestion:
https://lore.kernel.org/qemu-devel/20220510235439.54775-1-muriloo@linux.ibm.com/
Thank you for your review.
--
Murilo
prev parent reply other threads:[~2022-05-11 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 1:16 [PATCH v2] mos6522: fix linking error when CONFIG_MOS6522 is not set Murilo Opsfelder Araujo
2022-05-10 7:24 ` Thomas Huth
2022-05-11 0:01 ` Murilo Opsfelder Araújo [this message]
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=d0fa9d1f-bc09-5068-b222-f94cc5bc7810@linux.ibm.com \
--to=muriloo@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=dgilbert@redhat.com \
--cc=farosas@linux.ibm.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mopsfelder@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).