From: Michael Tokarev <mjt@tls.msk.ru>
To: Song Gao <gaosong@loongson.cn>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, WANG Rui <wangrui@loongson.cn>,
Bibo Mao <maobibo@loongson.cn>,
Clement Mathieu--Drif <clement.mathieu--drif@eviden.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PULL 1/2] target/loongarch: Guard 64-bit-only insn translation with TRANS64 macro
Date: Thu, 11 Sep 2025 13:30:45 +0300 [thread overview]
Message-ID: <84a347ed-3ad1-45d0-af08-1bb187390c0c@tls.msk.ru> (raw)
In-Reply-To: <fe6cc32a-1586-47bf-9ecc-ec8100372240@tls.msk.ru>
On 11.09.2025 13:04, Michael Tokarev wrote:
...
> The same applies to the second patch in this series, btw, -- the second
> patch also does not apply to 10.0.x directly because 10.0 lacks commit
> ab9bbee3c7da3 "hw/intc/loongarch_pch: Modify name of some registers" --
> the commit is just some code renames, it does not change actual code, so
> it is a no-op, but it makes subsequent changes to not apply directly.
> I think I'll pick ab9bbee3c7da3 and the next one, 4f0f2ab5640ef
> "hw/intc/loongarch_pch: Modify register name PCH_PIC_xxx_OFFSET..",
> to 10.0.x too.
And nope, the second patch ("loongarch_pch_pic: Fix ubsan warning and
endianness issue") is a bit more involved in 10.0.x, since 10.0 also
misses a6fdd0032ce5c7c "loongarch_pch: Use generic write callback for
iomem8 region", which is one from larger refactoring series. Sigh.
loongarch is a fast-moving target still.. :)
Thanks,
/mjt
next prev parent reply other threads:[~2025-09-11 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:02 [PULL 0/2] loongarch-to-apply queue Song Gao
2025-08-28 12:02 ` [PULL 1/2] target/loongarch: Guard 64-bit-only insn translation with TRANS64 macro Song Gao
2025-09-11 10:04 ` Michael Tokarev
2025-09-11 10:30 ` Michael Tokarev [this message]
2025-09-11 13:08 ` gaosong
2025-08-28 12:02 ` [PULL 2/2] hw/intc/loongarch_pch_pic: Fix ubsan warning and endianness issue Song Gao
2025-08-29 8:28 ` [PULL 0/2] loongarch-to-apply queue 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=84a347ed-3ad1-45d0-af08-1bb187390c0c@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=clement.mathieu--drif@eviden.com \
--cc=gaosong@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@redhat.com \
--cc=wangrui@loongson.cn \
/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).