From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: Yogesh Vyas <yvyas1991@gmail.com>,
BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v2] pc-bios/dtb/pegasos*.dtb: Fix compiled dtb blobs
Date: Sun, 9 Nov 2025 18:03:57 +0530 [thread overview]
Message-ID: <04809969-5de3-4cd5-9919-405a0b2cf09a@linux.ibm.com> (raw)
In-Reply-To: <b32eeb42-66b4-4dff-accd-cab187ef073b@gmail.com>
On 11/9/25 01:41, Yogesh Vyas wrote:
> Hi Balaton,
>
> I just tested after applying this patch and it seems to solve the issue.
> Thank you very much.
>
> Reported-by: Yogesh Vyas <yvyas1991@gmail.com>
> Tested-by: Yogesh Vyas <yvyas1991@gmail.com>
>
> On 11/9/25 1:07 AM, BALATON Zoltan wrote:
>> When adding these files somehow an incomplete version was committed.
>> Regenerate and update these dtb files to match the dts which fixes
>> problems caused by missing nodes in the dtb.
>>
>> Fixes: 9099b430a4 (hw/ppc/pegasos2: Change device tree generation)
>> Fixes: 3c21f9dfcf (hw/ppc/pegasos2: Add VOF support for pegasos1)
>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>> ---
>> v2: updated commit message to mention the two commits fixed here
>>
>> pc-bios/dtb/pegasos1.dtb | Bin 857 -> 1975 bytes
>> pc-bios/dtb/pegasos2.dtb | Bin 1701 -> 2963 bytes
>> 2 files changed, 0 insertions(+), 0 deletions(-)
>>
Queued, thanks.
prev parent reply other threads:[~2025-11-09 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 19:37 [PATCH v2] pc-bios/dtb/pegasos*.dtb: Fix compiled dtb blobs BALATON Zoltan
2025-11-08 20:11 ` Yogesh Vyas
2025-11-09 12:33 ` Harsh Prateek Bora [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=04809969-5de3-4cd5-9919-405a0b2cf09a@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=balaton@eik.bme.hu \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=yvyas1991@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.