From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v3 00/30] QAPI patches for 2018-03-01
Date: Fri, 2 Mar 2018 16:55:53 +0000 [thread overview]
Message-ID: <CAFEAcA_bJRe-iWra+8othHo0xo1TYjKp3mmU2TF1Buab1==7LQ@mail.gmail.com> (raw)
In-Reply-To: <20180302153205.9107-1-eblake@redhat.com>
On 2 March 2018 at 15:31, Eric Blake <eblake@redhat.com> wrote:
> The following changes since commit 2e7b766594e17f786a6b2e5be690bc5b43ce6036:
>
> Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2018-03-01' into staging (2018-03-02 12:39:13 +0000)
>
> are available in the Git repository at:
>
> git://repo.or.cz/qemu/ericb.git tags/pull-qapi-2018-03-01-v3
>
> for you to fetch changes up to cfe6a7fc6da20349ef62966c437f18ed6c49fcd5:
>
> qapi: Don't create useless directory qapi-generated (2018-03-02 09:01:40 -0600)
>
> v3: (attempt to) fix warnings about empty .o files on OSX toolchain [Peter]
> (sending just the changed patch)
>
> ----------------------------------------------------------------
> qapi patches for 2018-03-01
>
> - Markus Armbruster: Modularize generated QAPI code
>
As I suspected, this isn't sufficient to silence the warnings.
thanks
-- PMM
next prev parent reply other threads:[~2018-03-02 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:31 [Qemu-devel] [PULL v3 00/30] QAPI patches for 2018-03-01 Eric Blake
2018-03-02 15:31 ` [Qemu-devel] [PULL v3 23/30] qapi: Generate separate .h, .c for each module Eric Blake
2018-03-02 16:55 ` Peter Maydell [this message]
2018-03-02 18:25 ` [Qemu-devel] [PULL v3 00/30] QAPI patches for 2018-03-01 Eric Blake
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='CAFEAcA_bJRe-iWra+8othHo0xo1TYjKp3mmU2TF1Buab1==7LQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=eblake@redhat.com \
--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).