From: Peter Maydell <peter.maydell@linaro.org>
To: "KONRAD Frédéric" <fred.konrad@greensocs.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Edgar Iglesias <edgar.iglesias@xilinx.com>,
Alistair Francis <alistair.francis@xilinx.com>,
Mark Burton <mark.burton@greensocs.com>
Subject: Re: [Qemu-devel] [RFC PATCH 08/11] zynqmp_crf: fix against AF_EX32 changes
Date: Fri, 29 Jul 2016 14:48:52 +0100 [thread overview]
Message-ID: <CAFEAcA8D+BWgw8bU=FB1v223aFF4Lax60xpjEha6nGB_oZd7uw@mail.gmail.com> (raw)
In-Reply-To: <1465835259-21449-9-git-send-email-fred.konrad@greensocs.com>
On 13 June 2016 at 17:27, <fred.konrad@greensocs.com> wrote:
> From: KONRAD Frederic <fred.konrad@greensocs.com>
>
> This seems to be due to a difference between the AF_EX32 define.
>
> Signed-off-by: KONRAD Frederic <fred.konrad@greensocs.com>
> ---
> hw/misc/xilinx_zynqmp_crf.c | 354 ++++++++++++++++++++++----------------------
> 1 file changed, 177 insertions(+), 177 deletions(-)
This should just be squashed into the previous patch.
thanks
-- PMM
next prev parent reply other threads:[~2016-07-29 13:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 16:27 [Qemu-devel] [RFC PATCH 00/11] Clock framework API fred.konrad
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 01/11] qemu-clk: introduce qemu-clk qom object fred.konrad
2016-06-29 0:15 ` Alistair Francis
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 02/11] qemu-clk: allow to attach a clock to a device fred.konrad
2016-06-29 0:15 ` Alistair Francis
2016-08-02 7:47 ` KONRAD Frederic
2016-08-04 0:26 ` Alistair Francis
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 03/11] qemu-clk: allow to bound two clocks together fred.konrad
2016-06-29 0:30 ` Alistair Francis
2016-07-29 13:39 ` Peter Maydell
2016-08-02 12:29 ` KONRAD Frederic
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 04/11] qdev-monitor: print the device's clock with info qtree fred.konrad
2016-06-29 0:33 ` Alistair Francis
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 05/11] docs: add qemu-clock documentation fred.konrad
2016-06-29 0:38 ` Alistair Francis
2016-08-02 9:29 ` KONRAD Frederic
2016-08-04 0:28 ` Alistair Francis
2016-07-29 13:47 ` Peter Maydell
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 06/11] introduce fixed-clock fred.konrad
2016-07-01 23:07 ` Alistair Francis
2016-08-02 11:56 ` KONRAD Frederic
2016-08-04 0:29 ` Alistair Francis
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 07/11] introduce zynqmp_crf fred.konrad
2016-06-29 0:41 ` Alistair Francis
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 08/11] zynqmp_crf: fix against AF_EX32 changes fred.konrad
2016-07-29 13:48 ` Peter Maydell [this message]
2016-08-02 12:34 ` KONRAD Frederic
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 09/11] zynqmp_crf: add the clock mechanism fred.konrad
2016-07-01 23:23 ` Alistair Francis
2016-08-02 12:26 ` KONRAD Frederic
2016-07-29 13:51 ` Peter Maydell
2016-08-03 7:38 ` KONRAD Frederic
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 10/11] zynqmp: add the zynqmp_crf to the platform fred.konrad
2016-07-01 23:11 ` Alistair Francis
2016-08-02 12:36 ` KONRAD Frederic
2016-06-13 16:27 ` [Qemu-devel] [RFC PATCH 11/11] zynqmp: add reference clock fred.konrad
2016-07-29 13:59 ` [Qemu-devel] [RFC PATCH 00/11] Clock framework API Peter Maydell
2016-08-02 6:28 ` KONRAD Frederic
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='CAFEAcA8D+BWgw8bU=FB1v223aFF4Lax60xpjEha6nGB_oZd7uw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@xilinx.com \
--cc=edgar.iglesias@xilinx.com \
--cc=fred.konrad@greensocs.com \
--cc=mark.burton@greensocs.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).