From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-trivial@nongnu.org, "Emilio G . Cota" <cota@braap.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] plugins: Move declarations around and rename 'hwaddr' argument
Date: Tue, 12 May 2020 19:44:28 +0100 [thread overview]
Message-ID: <875zd1f0xf.fsf@linaro.org> (raw)
In-Reply-To: <20200510171119.20827-1-f4bug@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> Rename qemu_plugin_hwaddr_is_io() 'hwaddr' argument to later
> allow declaration of the 'hwaddr' type to be poisoned (see [*]).
>
> [*] https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg02254.html
> "exec/cpu: Poison 'hwaddr' type in user-mode emulation"
Queued to plugins/next, thanks.
>
> Philippe Mathieu-Daudé (3):
> qemu/plugin: Trivial code movement
> qemu/plugin: Move !CONFIG_PLUGIN stubs altogether
> qemu/qemu-plugin: Make qemu_plugin_hwaddr_is_io() hwaddr argument
> const
>
> include/qemu/plugin.h | 65 ++++++++++++++++++--------------------
> include/qemu/qemu-plugin.h | 2 +-
> plugins/api.c | 4 +--
> 3 files changed, 34 insertions(+), 37 deletions(-)
--
Alex Bennée
prev parent reply other threads:[~2020-05-12 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 17:11 [PATCH 0/3] plugins: Move declarations around and rename 'hwaddr' argument Philippe Mathieu-Daudé
2020-05-10 17:11 ` [PATCH 1/3] qemu/plugin: Trivial code movement Philippe Mathieu-Daudé
2020-05-10 17:11 ` [PATCH 2/3] qemu/plugin: Move !CONFIG_PLUGIN stubs altogether Philippe Mathieu-Daudé
2020-05-10 17:11 ` [PATCH 3/3] qemu/qemu-plugin: Make qemu_plugin_hwaddr_is_io() hwaddr argument const Philippe Mathieu-Daudé
2020-05-10 20:14 ` [PATCH 0/3] plugins: Move declarations around and rename 'hwaddr' argument Emilio G. Cota
2020-05-12 18:44 ` Alex Bennée [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=875zd1f0xf.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).