All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <th.huth@posteo.eu>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PULL SUBSYSTEM pseries 0/1] pseries: Update SLOF firmware image to release 20260618
Date: Thu, 25 Jun 2026 16:59:43 +0000	[thread overview]
Message-ID: <20260625185941.421b952f@tpx1> (raw)
In-Reply-To: <22607674-c519-4384-a51e-51da9e7c9967@linux.ibm.com>

Am Tue, 23 Jun 2026 15:06:50 +0530
schrieb Harsh Prateek Bora <harshpb@linux.ibm.com>:

> Hi Thomas,
> 
> On 18/06/26 1:56 pm, Thomas Huth wrote:
> >   Hi Harsh, hi Nicholas!
> > 
> > The following changes since commit c7cf7c810153d6f5f31aa2d5c0dee9087f6b4dff:
> > 
> >    Merge tag 'firmware-20260617-pull-request' of https://gitlab.com/kraxel/qemu into staging (2026-06-17 10:17:29 -0400)
> > 
> > are available in the Git repository at:
> > 
> >    https://gitlab.com/huth/qemu.git tags/qemu-slof-20260618
...> 
> Looks like updating VERSION file was missed before building the slof.bin
> (as checked in gitlab repo). Also, I see below FW version (git-xxx)
> during boot:
> 
> SLOF 
> ********************************************************************** 
>   
> 
> QEMU Starting 
>   
> 
>   Build Date = Jun 18 2026 08:06:19 
>   
> 
>   FW Version = git-def1516ec9340518 
>   
> 
>   Press "s" to enter Open Firmware.
> 
> 
> Whereas, earlier, it used to appear like proper release timestamp:
> 
> 
> SLOF **********************************************************************
> QEMU Starting
>   Build Date = Oct 26 2025 18:45:22
>   FW Version = release 20251026
>   Press "s" to enter Open Firmware.
> 
> Curious to know if it's only the VERSION update needed or something more 
> (make args) ?

As you just mentioned in chat, I also missed to update the submodule :-/

Sorry for messing up this time, I will send a v2 in the next days when I
got some spare time....

 Thomas


      reply	other threads:[~2026-06-25 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18  8:26 [PULL SUBSYSTEM pseries 0/1] pseries: Update SLOF firmware image to release 20260618 Thomas Huth
2026-06-18  8:26 ` [PULL SUBSYSTEM pseries 1/1] " Thomas Huth
2026-06-18 17:53 ` [PULL SUBSYSTEM pseries 0/1] " Stefan Hajnoczi
2026-06-18 18:34   ` Peter Maydell
2026-06-18 19:01     ` Stefan Hajnoczi
2026-06-18 20:26       ` Stefan Hajnoczi
2026-06-23  9:36 ` Harsh Prateek Bora
2026-06-25 16:59   ` Thomas Huth [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=20260625185941.421b952f@tpx1 \
    --to=th.huth@posteo.eu \
    --cc=harshpb@linux.ibm.com \
    --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 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.