From: Peter Maydell <peter.maydell@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH v6 0/6] arm: Make use of DEFINE_PROP_LINK
Date: Tue, 5 Sep 2017 16:47:02 +0100 [thread overview]
Message-ID: <CAFEAcA8ULL2=DjcuT5BRipKGm6t95VD-oT6Uh8eYAcTKGKySeQ@mail.gmail.com> (raw)
In-Reply-To: <20170905131149.10669-1-famz@redhat.com>
On 5 September 2017 at 14:11, Fam Zheng <famz@redhat.com> wrote:
> v6: Rebase and resend v5: Add Philippe's rev-bys and fix one typo in bitband
> patch.
>
> This is the arm part that was left out from:
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg04006.html
>
> Make use of the new DEFINE_PROP_LINK, in favor of open coded the
> object_property_add_link. The advantage of it is the property now get reflected
> in the info qtree output, for a bit more introspectability.
>
Applied to target-arm.next, thanks.
-- PMM
prev parent reply other threads:[~2017-09-05 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 13:11 [Qemu-devel] [PATCH v6 0/6] arm: Make use of DEFINE_PROP_LINK Fam Zheng
2017-09-05 13:11 ` [Qemu-devel] [PATCH v6 1/6] armv7m: Convert bitband.source-memory to DEFINE_PROP_LINK Fam Zheng
2017-09-05 13:11 ` [Qemu-devel] [PATCH v6 2/6] armv7m: Convert armv7m.memory " Fam Zheng
2017-09-05 13:11 ` [Qemu-devel] [PATCH v6 3/6] gicv3: Convert " Fam Zheng
2017-09-05 13:44 ` Philippe Mathieu-Daudé
2017-09-05 15:35 ` Fam Zheng
2017-09-05 16:20 ` Philippe Mathieu-Daudé
2017-09-05 13:11 ` [Qemu-devel] [PATCH v6 4/6] xlnx_zynqmp: " Fam Zheng
2017-09-05 13:11 ` [Qemu-devel] [PATCH v6 5/6] xilinx_axienet: " Fam Zheng
2017-09-05 13:11 ` [Qemu-devel] [PATCH v6 6/6] xilinx_axidma: " Fam Zheng
2017-09-05 15:47 ` Peter Maydell [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='CAFEAcA8ULL2=DjcuT5BRipKGm6t95VD-oT6Uh8eYAcTKGKySeQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-arm@nongnu.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).