From: Palmer Dabbelt <palmer@sifive.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: [Qemu-devel] [PULL] A Single RISC-V Patch for 3.1-rc1
Date: Thu, 8 Nov 2018 10:33:05 -0800 [thread overview]
Message-ID: <20181108183306.4361-1-palmer@sifive.com> (raw)
The following changes since commit a7ce790a029bd94eb320d8c69f38900f5233997e:
tcg/tcg-op.h: Add multiple include guard (2018-11-08 15:15:32 +0000)
are available in the Git repository at:
git://github.com/riscv/riscv-qemu.git tags/riscv-for-master-3.1-rc1
for you to fetch changes up to 00a014ac01feac875468d38c376f7e06f050f992:
riscv: spike: Fix memory leak in the board init (2018-11-08 08:41:06 -0800)
----------------------------------------------------------------
A Single RISC-V Patch for 3.1-rc1
This tag contains a single patch that I'd like to target for rc1: a fix
for a memory leak that was detected by static code analysis.
There are still three patch sets that I'd like to try to get up for 3.1:
* The patch set Basian just published that contains fixes for a pair of
issues he found when converting our port to decodetree.
* An as-of-yet-unwritten fix to the third issue that Basian pointed out.
* A fix to our fflags bug, which is currently coupled to some CSR
refactoring that I don't think is OK for 3.1.
I'm at Plumbers next week (and I think Alistair is there too?), but I'll
try to find a way to squeeze in as much as possible.
----------------------------------------------------------------
Alistair Francis (1):
riscv: spike: Fix memory leak in the board init
hw/riscv/spike.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2018-11-08 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 18:33 Palmer Dabbelt [this message]
2018-11-08 18:33 ` [Qemu-devel] [PULL] riscv: spike: Fix memory leak in the board init Palmer Dabbelt
2018-11-08 18:38 ` [Qemu-devel] [PULL] A Single RISC-V Patch for 3.1-rc1 Alistair Francis
2018-11-08 18:52 ` Palmer Dabbelt
2018-11-09 10:53 ` Peter Maydell
2018-11-09 19:01 ` Palmer Dabbelt
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=20181108183306.4361-1-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).