All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <peter.marko@siemens.com>, <openembedded-core@lists.openembedded.org>
Cc: "Ross Burton" <ross.burton@arm.com>, "Jon Mason" <jon.mason@arm.com>
Subject: Re: [OE-core] [PATCH 1/2] grub: update upstream-check
Date: Tue, 17 Nov 2026 19:42:45 +0100	[thread overview]
Message-ID: <DMXPGW66H9CP.1ATNO2XD1FDS3@bootlin.com> (raw)
In-Reply-To: <20261116224959.197150-1-peter.marko@siemens.com>

On Mon Nov 16, 2026 at 11:49 PM CET, Peter Marko via openembedded-core wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> Repository has moved, see [1].
> Old location does not contain new releases anymore.
>
> [1] https://www.phoronix.com/news/GNU-GRUB-To-FreeDesktop
>
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---

Hi Peter,

Thanks for your patches. It looks like this is breaking meta-arm builds.
Technically, this does not prevent from merging it into
openembedded-core, yet I'm a bit surprised by that.

If any of you has an idea of why qemu is failing here, I'd be happy to
hear about it. The QEMU boot log just contains what looks like a few
aborted boots:

NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.14.9(release):lts-v2.14.9-dirty
NOTICE:  BL1: Built : 06:59:21, Sep 25 2026
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.14.9(release):lts-v2.14.9-dirty
NOTICE:  BL2: Built : 06:59:21, Sep 25 2026
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.14.9(release):lts-v2.14.9-dirty
NOTICE:  BL31: Built : 06:59:21, Sep 25 2026
UEFI firmware (version 1.0 built at 06:19:29 on Sep 22 2026)
ESC[2JESC[004DESC[=3hESC[2JESC[009DNOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.14.9(release):lts-v2.14.9-dirty
NOTICE:  BL1: Built : 06:59:21, Sep 25 2026
...
(the whole boot sequence is repeated 5 times)

https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/4883

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2026-11-17 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 22:49 [PATCH 1/2] grub: update upstream-check Peter Marko
2026-11-16 22:49 ` [PATCH 2/2] grub: upgrade 2.14 -> 2.16 Peter Marko
2026-11-17 18:42 ` Mathieu Dubois-Briand [this message]
2026-11-17 20:53   ` [OE-core] [PATCH 1/2] grub: update upstream-check Marko, Peter
2026-11-17 21:14     ` Marko, Peter
2026-11-18  8:31       ` Mathieu Dubois-Briand

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=DMXPGW66H9CP.1ATNO2XD1FDS3@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=jon.mason@arm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.marko@siemens.com \
    --cc=ross.burton@arm.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.