From: Stafford Horne <shorne@gmail.com>
To: QEMU Development <qemu-devel@nongnu.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Richard Henderson <richard.henderson@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Stafford Horne <shorne@gmail.com>
Subject: [PULL 0/1] OpenRISC Updates 2026-09-13
Date: Sun, 13 Sep 2026 08:03:02 +0100 [thread overview]
Message-ID: <20260913070303.1010504-1-shorne@gmail.com> (raw)
Hello,
Please consider for pull,
The following changes since commit d43c2d5f89db70359a7b3a7e2ad7098fcc0165ef:
Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu into staging (2026-09-11 12:04:42 -1000)
are available in the Git repository at:
https://github.com/stffrdhrn/qemu.git tags/or1k-updates-20260913
for you to fetch changes up to cfaf6a1edd8803f0334007dbbff9ca5eb293e98b:
target/or1k: Implement l.extws and l.extwz (2026-09-12 08:31:14 +0100)
----------------------------------------------------------------
OpenRISC Updates 2026-09-13
One patch:
- Missing instruction definitions for word sign extension.
----------------------------------------------------------------
Ali Ahmet Memiş (1):
target/or1k: Implement l.extws and l.extwz
target/or1k/disas.c | 2 ++
target/or1k/insns.decode | 2 ++
target/or1k/translate.c | 14 ++++++++++++++
3 files changed, 18 insertions(+)
Ali Ahmet Memiş (1):
target/or1k: Implement l.extws and l.extwz
target/or1k/disas.c | 2 ++
target/or1k/insns.decode | 2 ++
target/or1k/translate.c | 14 ++++++++++++++
3 files changed, 18 insertions(+)
--
2.53.0
next reply other threads:[~2026-09-13 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 7:03 Stafford Horne [this message]
2026-09-13 7:03 ` [PULL 1/1] target/or1k: Implement l.extws and l.extwz Stafford Horne
2026-09-14 3:09 ` [PULL 0/1] OpenRISC Updates 2026-09-13 Richard Henderson
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=20260913070303.1010504-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=linux-openrisc@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.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).