From: Peter Maydell <peter.maydell@linaro.org>
To: Tong Ho <tongh@xilinx.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alistair Francis <alistair@alistair23.me>
Subject: Re: [PATCH v3 0/9] hw/nvram: hw/arm: Introduce Xilinx eFUSE and BBRAM
Date: Mon, 1 Nov 2021 11:22:37 +0000 [thread overview]
Message-ID: <CAFEAcA8CYB_rd9BotA3jE3bxSi-Nv_fL8uDz8PxsgxNsa4KR1g@mail.gmail.com> (raw)
In-Reply-To: <BYAPR02MB40381A62103A15406DB2132BCDAE9@BYAPR02MB4038.namprd02.prod.outlook.com>
On Mon, 4 Oct 2021 at 16:54, Tong Ho <tongh@xilinx.com> wrote:
>
> Hi Peter,
>
> I will follow up with patches to fix the memory leaks.
>
> Where can I get a copy of the Coverity reports that have the 10 issues you indicated?
They're on https://scan.coverity.com/projects/qemu?tab=overview
You'll need to create an account and request access there.
-- PMM
prev parent reply other threads:[~2021-11-01 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 5:23 [PATCH v3 0/9] hw/nvram: hw/arm: Introduce Xilinx eFUSE and BBRAM Tong Ho
2021-09-17 5:23 ` [PATCH v3 1/9] hw/nvram: Introduce Xilinx eFuse QOM Tong Ho
2021-09-17 5:23 ` [PATCH v3 2/9] hw/nvram: Introduce Xilinx Versal eFuse device Tong Ho
2021-09-17 5:23 ` [PATCH v3 3/9] hw/nvram: Introduce Xilinx ZynqMP " Tong Ho
2021-09-17 5:23 ` [PATCH v3 4/9] hw/nvram: Introduce Xilinx battery-backed ram Tong Ho
2021-09-17 5:23 ` [PATCH v3 5/9] hw/arm: xlnx-versal-virt: Add Xilinx BBRAM device Tong Ho
2021-09-17 5:23 ` [PATCH v3 6/9] hw/arm: xlnx-versal-virt: Add Xilinx eFUSE device Tong Ho
2021-09-17 5:23 ` [PATCH v3 7/9] hw/arm: xlnx-zcu102: Add Xilinx BBRAM device Tong Ho
2021-09-17 5:23 ` [PATCH v3 8/9] hw/arm: xlnx-zcu102: Add Xilinx eFUSE device Tong Ho
2021-09-17 5:24 ` [PATCH v3 9/9] docs/system/arm: xlnx-versal-virt: BBRAM and eFUSE Usage Tong Ho
2021-09-27 11:07 ` [PATCH v3 0/9] hw/nvram: hw/arm: Introduce Xilinx eFUSE and BBRAM Peter Maydell
2021-10-02 10:28 ` Peter Maydell
2021-10-04 15:54 ` Tong Ho
2021-11-01 11:22 ` 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=CAFEAcA8CYB_rd9BotA3jE3bxSi-Nv_fL8uDz8PxsgxNsa4KR1g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tongh@xilinx.com \
/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).