From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH 07/13] hw/ppc/pegasos2: Add south bridge pointer in the machine state
Date: Tue, 10 Jun 2025 09:28:23 +0200 [thread overview]
Message-ID: <f1d82662-26c1-4d8f-a5a7-5a01a63b4231@linaro.org> (raw)
In-Reply-To: <0e77e44fe99c3cecbe17d6a8b697c996d2a0923c.1746139668.git.balaton@eik.bme.hu>
On 2/5/25 01:20, BALATON Zoltan wrote:
> Add field for the south bridge in machine state to have both north and
> south bridges in it.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
> hw/ppc/pegasos2.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-06-10 7:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 23:20 [PATCH 00/13] Pegasos2 clean up and pegasos1 emulation BALATON Zoltan
2025-05-01 23:20 ` [PATCH 01/13] hw/boards: Extend DEFINE_MACHINE macro to cover more use cases BALATON Zoltan
2025-06-10 7:24 ` Philippe Mathieu-Daudé
2025-06-10 11:38 ` BALATON Zoltan
2025-05-01 23:20 ` [PATCH 02/13] ppc/vof: Make nextprop behave more like Open Firmware BALATON Zoltan
2025-05-01 23:20 ` [PATCH 03/13] hw/ppc/pegasos2: Remove explicit name properties from device tree BALATON Zoltan
2025-05-01 23:20 ` [PATCH 04/13] hw/ppc/pegasos2: Change device tree generation BALATON Zoltan
2025-05-01 23:20 ` [PATCH 05/13] hw/ppc/pegasos2: Remove fdt pointer from machine state BALATON Zoltan
2025-05-01 23:20 ` [PATCH 06/13] hw/ppc/pegasos2: Rename mv field in " BALATON Zoltan
2025-06-10 7:28 ` Philippe Mathieu-Daudé
2025-05-01 23:20 ` [PATCH 07/13] hw/ppc/pegasos2: Add south bridge pointer in the " BALATON Zoltan
2025-06-10 7:28 ` Philippe Mathieu-Daudé [this message]
2025-05-01 23:20 ` [PATCH 08/13] hw/ppc/pegasos2: Move PCI IRQ routing setup to a function BALATON Zoltan
2025-05-01 23:20 ` [PATCH 09/13] hw/ppc/pegasos2: Move hardware specific parts out of machine reset BALATON Zoltan
2025-05-01 23:20 ` [PATCH 10/13] hw/ppc/pegasos2: Introduce abstract superclass BALATON Zoltan
2025-05-01 23:20 ` [PATCH 11/13] hw/ppc/pegasos2: Add bus frequency to machine state BALATON Zoltan
2025-05-01 23:20 ` [PATCH 12/13] hw/ppc/pegasos2: Add Pegasos I emulation BALATON Zoltan
2025-05-01 23:20 ` [PATCH 13/13] hw/ppc/pegasos2: Add VOF support for pegasos1 BALATON Zoltan
2025-05-22 22:31 ` [PATCH 00/13] Pegasos2 clean up and pegasos1 emulation BALATON Zoltan
2025-06-02 12:27 ` BALATON Zoltan
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=f1d82662-26c1-4d8f-a5a7-5a01a63b4231@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).