From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Cc: Geoff Levand <geoff@infradead.org>
Subject: Re: [PATCH 0/3] powerpc/ps3: Fixes for lv1 hcall assembly
Date: Mon, 26 Feb 2024 16:56:48 +1100 [thread overview]
Message-ID: <170892700815.3915597.14761384936011707576.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231227072405.63751-1-npiggin@gmail.com>
On Wed, 27 Dec 2023 17:24:02 +1000, Nicholas Piggin wrote:
> This (hopefully) fixes the ELFv2 bug that Geoff reported, with patch
> 1. And a couple of other possible improvements I noticed.
>
> I don't have a PS3 setup[*] so I have only compile tested these, I'm
> sorry.
>
> [*] Is RPCS3 usable for this kind of thing?
>
> [...]
Applied to powerpc/next.
[1/3] powerpc/ps3: Fix lv1 hcall assembly for ELFv2 calling convention
https://git.kernel.org/powerpc/c/6735fef14c1f089ae43fd6d43add818b7ff682a8
[2/3] powerpc/ps3: lv1 hcall code use symbolic constant for LR save offset
https://git.kernel.org/powerpc/c/d901473c4dd0198d2d60553ea483d632175af4ea
[3/3] powerpc/ps3: Make real stack frames for LV1 hcalls
https://git.kernel.org/powerpc/c/28b2ed86750cf5be86d19dd6ff236b23e98b255d
cheers
prev parent reply other threads:[~2024-02-26 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 7:24 [PATCH 0/3] powerpc/ps3: Fixes for lv1 hcall assembly Nicholas Piggin
2023-12-27 7:24 ` [PATCH 1/3] powerpc/ps3: Fix lv1 hcall assembly for ELFv2 calling convention Nicholas Piggin
2023-12-27 7:24 ` [PATCH 2/3] powerpc/ps3: lv1 hcall code use symbolic constant for LR save offset Nicholas Piggin
2023-12-27 7:24 ` [PATCH 3/3] powerpc/ps3: Make real stack frames for LV1 hcalls Nicholas Piggin
2023-12-27 9:50 ` [PATCH 0/3] powerpc/ps3: Fixes for lv1 hcall assembly Geoff Levand
2023-12-29 8:53 ` Geoff Levand
2024-02-26 5:56 ` Michael Ellerman [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=170892700815.3915597.14761384936011707576.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=geoff@infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).