qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Denis V. Lunev" <den@openvz.org>,
	qemu-devel@nongnu.org, Pavel Butsykin <pbutsykin@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] monitor: remove target-specific code from monitor.c
Date: Tue, 8 Sep 2015 09:13:51 -0400	[thread overview]
Message-ID: <20150908091351.19c2e5d6@redhat.com> (raw)
In-Reply-To: <92042290.27379798.1441717496978.JavaMail.zimbra@redhat.com>

On Tue, 8 Sep 2015 09:04:56 -0400 (EDT)
Paolo Bonzini <pbonzini@redhat.com> wrote:

> 
> > > This should be added in patch 4, not now.
> > > 
> > > > +const MonitorDef *target_monitor_defs(void) __attribute__((weak));
> > > > +
> > > > +const MonitorDef *target_monitor_defs(void)
> > > > +{
> > > > +    return NULL;
> > > > +}
> > > 
> > > Weak symbols do not work on all platforms.  Luckily, making libqemustub
> > > a static library gets exactly the same result without the need for weak
> > > symbols: the definition from the QEMU object files will hide the stub.
> > > 
> > > You just need to remove __attribute__((weak)), and it should just work.
> > > 
> > > Otherwise, the patches look good to me.  Luiz, do you have time to post
> > > a pull request for v4, or do you want to pass HMP maintainership as well
> > > to someone else?
> > 
> > It would be great to pass it to someone else.
> 
> I can take the next version of these patches then.  

Thanks a lot! These are the patches I have pending for review:

- [PATCH qemu 0/2] monitor/ppc: Print correct SPRs
- [PATCH] trace-events: Add hmp completion
- [PATCH v3 0/4] Move target- and device specific code from monitor

> However, please make that
> someone else also be someone other than me. :-)

Well, we've always been short on maintainers...

  reply	other threads:[~2015-09-08 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  7:09 [Qemu-devel] [PATCH v3 0/4] Move target- and device specific code from monitor Denis V. Lunev
2015-09-08  7:09 ` [Qemu-devel] [PATCH 1/4] hmp-commands-info: move info_cmds content out of monitor.c Denis V. Lunev
2015-09-08  7:09 ` [Qemu-devel] [PATCH 2/4] monitor: remove target-specific code from monitor.c Denis V. Lunev
2015-09-08  9:54   ` Paolo Bonzini
2015-09-08 10:13     ` Fam Zheng
2015-09-09 11:24       ` Pavel Butsykin
2015-09-08 13:03     ` Luiz Capitulino
2015-09-08 13:04       ` Paolo Bonzini
2015-09-08 13:13         ` Luiz Capitulino [this message]
2015-09-08 13:51           ` Paolo Bonzini
2015-09-09 12:52             ` Stefan Hajnoczi
2015-09-08  7:09 ` [Qemu-devel] [PATCH 3/4] hmp-commands.hx: fix end of table info Denis V. Lunev
2015-09-08  7:09 ` [Qemu-devel] [PATCH 4/4] monitor: added generation of documentation for hmp-commands-info.hx Denis V. Lunev
  -- strict thread matches above, loose matches on Subject: below --
2015-09-10 15:38 [Qemu-devel] [PATCH v4 0/4] Move target- and device specific code from monitor Denis V. Lunev
2015-09-10 15:38 ` [Qemu-devel] [PATCH 2/4] monitor: remove target-specific code from monitor.c Denis V. Lunev

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=20150908091351.19c2e5d6@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=den@openvz.org \
    --cc=pbonzini@redhat.com \
    --cc=pbutsykin@virtuozzo.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).