From: Alistair Francis <alistair.francis@opensource.wdc.com>
To: qemu-devel@nongnu.org
Cc: alistair23@gmail.com, Alistair Francis <alistair.francis@wdc.com>
Subject: [PULL 0/1] riscv-to-apply queue
Date: Tue, 2 Aug 2022 09:02:11 +1000 [thread overview]
Message-ID: <20220801230212.3406689-1-alistair.francis@opensource.wdc.com> (raw)
From: Alistair Francis <alistair.francis@wdc.com>
The following changes since commit 0e0c2cf6de0bc6538840837c63b25817cd417347:
Merge tag 'pull-target-arm-20220801' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (2022-08-01 12:00:08 -0700)
are available in the Git repository at:
git@github.com:alistair23/qemu.git tags/pull-riscv-to-apply-20220802
for you to fetch changes up to 1eaa63429a9944265c92efdb94c02fabb231f564:
linux-user/riscv: Align signal frame to 16 bytes (2022-08-02 08:56:49 +1000)
----------------------------------------------------------------
Seventh RISC-V PR for QEMU 7.1
This is a second PR to go in for RC1. It fixes a bug we have had
for awhile, but it's a simple fix so let's pull it in for RC1.
* linux-user/riscv: Align signal frame to 16 bytes
----------------------------------------------------------------
Richard Henderson (1):
linux-user/riscv: Align signal frame to 16 bytes
linux-user/riscv/signal.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
next reply other threads:[~2022-08-01 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 23:02 Alistair Francis [this message]
2022-08-01 23:02 ` [PULL 1/1] linux-user/riscv: Align signal frame to 16 bytes Alistair Francis
2022-08-02 13:36 ` [PULL 0/1] riscv-to-apply queue Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2023-07-23 9:34 Alistair Francis
2023-07-24 13:21 ` Peter Maydell
2024-08-19 4:43 Alistair Francis
2024-08-19 7:46 ` Richard Henderson
2025-04-07 5:12 Alistair Francis
2025-04-08 0:38 ` Stefan Hajnoczi
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=20220801230212.3406689-1-alistair.francis@opensource.wdc.com \
--to=alistair.francis@opensource.wdc.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.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).