From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Kamil Rytarowski <n54@gmx.com>,
"patches@linaro.org" <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] Fix NetBSD build (don't build ivshmem tools)
Date: Thu, 20 Jul 2017 16:35:12 +0100 [thread overview]
Message-ID: <CAFEAcA-QEpAuh-CTrC-XvHHAWwhCT85M9Pwn3fAngpXDK8F7Fw@mail.gmail.com> (raw)
In-Reply-To: <87zibz2w4c.fsf@dusky.pond.sub.org>
On 20 July 2017 at 12:20, Markus Armbruster <armbru@redhat.com> wrote:
> Regardless of my inability to find CONFIG_IVSHMEM confusing (see PATCH
> 1), series
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
Thanks; patchset applied to master.
-- PMM
next prev parent reply other threads:[~2017-07-20 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 8:33 [Qemu-devel] [PATCH 0/3] Fix NetBSD build (don't build ivshmem tools) Peter Maydell
2017-07-14 8:33 ` [Qemu-devel] [PATCH 1/3] configure: Rename CONFIG_IVSHMEM to CONFIG_IVSHMEM_DEVICE Peter Maydell
2017-07-20 11:17 ` Markus Armbruster
2017-07-20 11:54 ` Peter Maydell
2017-07-14 8:33 ` [Qemu-devel] [PATCH 2/3] configure: Use an explicit CONFIG_IVSHMEM rather than CONFIG_EVENTFD Peter Maydell
2017-07-14 8:33 ` [Qemu-devel] [PATCH 3/3] configure: Don't build ivshmem tools unless CONFIG_IVSHMEM is set Peter Maydell
2017-07-20 9:43 ` [Qemu-devel] [PATCH 0/3] Fix NetBSD build (don't build ivshmem tools) Peter Maydell
2017-07-20 11:20 ` Markus Armbruster
2017-07-20 15:35 ` Peter Maydell [this message]
2017-07-20 16:59 ` Kamil Rytarowski
-- strict thread matches above, loose matches on Subject: below --
2017-07-13 17:03 Peter Maydell
2017-07-13 18:40 ` Kamil Rytarowski
2017-07-13 20:12 ` Eric Blake
2017-07-14 8:34 ` 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=CAFEAcA-QEpAuh-CTrC-XvHHAWwhCT85M9Pwn3fAngpXDK8F7Fw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=n54@gmx.com \
--cc=patches@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).