From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Romain Naour <romain.naour@smile.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405
Date: Mon, 28 Oct 2024 22:12:54 +0100 [thread overview]
Message-ID: <20241028221254.37434add@windsurf> (raw)
In-Reply-To: <cefe2b8e2bcf392b1db0eddc3a38b2bc@free.fr>
On Mon, 28 Oct 2024 21:27:30 +0100
Julien Olivain <ju.o@free.fr> wrote:
> On my side (this series applied on top of branch master at 81e7806),
> this patch does not apply. This can be reproduced with:
>
> make qemu_aarch64_sbsa_defconfig
> make edk2-patch
>
> Which fails with output:
>
> Applying
> 0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch using
> patch:
I'd say there's a fairly high chance this isn't Romain's fault. I
haven't checked but I would guess that this EDK2 code base uses
DOS-style new lines (\r\n), and so the patches have those, but they get
stripped when going through the mailing list, making the patch
unapplicable.
> When we bumping boot/edk2, we usually also bump edk2-non-osi.
> See:
> https://gitlab.com/buildroot.org/buildroot/-/blob/master/package/edk2-non-osi/edk2-non-osi.mk?ref_type=heads#L7
>
> Even if it is not needed to fix the qemu_aarch64_sbsa_defconfig of
> this series, it would be better to keep all those components aligned.
>
> Could you check if edk2-non-osi needs to be updated too?
> If yes, could you update it?
> If no, could you add a mention that it does not need to?
>
> Maybe we could add a comment in boot/edk2/edk2.mk, before EDK2_VERSION.
> Something like:
>
> # When updating version, make sure to also update the edk2-platforms
> # and edk2-non-osi packages to their respective commit ID nearest to
> # the edk2 release.
I'll let Romain address this point before applying then.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-28 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 19:43 [Buildroot] [PATCH v2 1/3] configs/qemu_aarch64_sbsa_defconfig: update ATF to v2.11 Romain Naour via buildroot
2024-10-27 19:43 ` [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 Romain Naour via buildroot
2024-10-28 20:27 ` Julien Olivain
2024-10-28 21:12 ` Thomas Petazzoni via buildroot [this message]
2024-10-29 9:56 ` Romain Naour via buildroot
2024-10-29 20:51 ` Julien Olivain
2024-10-27 19:43 ` [Buildroot] [PATCH v2 3/3] configs/qemu_aarch64_sbsa_defconfig: switch to neoverse-n1 (armv8.2a) Romain Naour via buildroot
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=20241028221254.37434add@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.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