qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/10] QMP queue
Date: Mon, 11 May 2015 09:17:51 -0400	[thread overview]
Message-ID: <20150511091751.0aab2027@redhat.com> (raw)
In-Reply-To: <CAFEAcA9EBioNLXKJvoXvT97W0kTNOJ2L8zSuenTeJKK85-36Fw@mail.gmail.com>

On Mon, 11 May 2015 13:53:47 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:

> On 8 May 2015 at 14:34, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> > The following changes since commit f8340b360b9bc29d48716ba8aca79df2b9544979:
> >
> >   hw/ptimer: Do not artificially limit timers when using icount (2015-05-08 17:15:23 +1000)
> >
> > are available in the git repository at:
> >
> >   git://repo.or.cz/qemu/qmp-unstable.git tags/for-upstream
> >
> > for you to fetch changes up to 07972d16e3343dc62302b81efb018308f99f7a7a:
> >
> >   scripts: qmp-shell: Add verbose flag (2015-05-08 08:47:01 -0400)
> >
> > ----------------------------------------------------------------
> > QMP pull request
> 
> Hi. I'm afraid this doesn't build on win32:
> /home/petmay01/linaro/qemu-for-merges/monitor.c: In function ‘memory_search’:
> /home/petmay01/linaro/qemu-for-merges/monitor.c:1306: warning:
> implicit declaration of function ‘memmem’
> /home/petmay01/linaro/qemu-for-merges/monitor.c:1306: warning: nested
> extern declaration of ‘memmem’
> /home/petmay01/linaro/qemu-for-merges/monitor.c:1306: warning:
> assignment makes pointer from integer

Needless to say that I didn't build for win32. My bad.

Can you try again? I've dropped the offending patch and pushed
the tag again.

  reply	other threads:[~2015-05-11 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 13:34 [Qemu-devel] [PULL 00/10] QMP queue Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 01/10] monitor: add memory search commands s, sp Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 02/10] QJSON: Use OBJECT_CHECK Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 03/10] qobject: Clean up around qtype_code Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 04/10] qobject: Add a special null QObject Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 05/10] json-parser: Accept 'null' in QMP Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 06/10] MAINTAINERS: New maintainer for QMP and QAPI Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 07/10] scripts: qmp-shell: refactor helpers Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 08/10] scripts: qmp-shell: Expand support for QMP expressions Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 09/10] scripts: qmp-shell: add transaction subshell Luiz Capitulino
2015-05-08 13:34 ` [Qemu-devel] [PULL 10/10] scripts: qmp-shell: Add verbose flag Luiz Capitulino
2015-05-11 12:53 ` [Qemu-devel] [PULL 00/10] QMP queue Peter Maydell
2015-05-11 13:17   ` Luiz Capitulino [this message]
2015-05-12  9:40     ` Peter Maydell

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=20150511091751.0aab2027@redhat.com \
    --to=lcapitulino@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).