From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 78218433ad12bd4e34e50fac8f72668eac988eb2
Date: Tue, 18 Apr 2023 07:46:44 +0000 [thread overview]
Message-ID: <4Q0wwh268Bz2xgF@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 78218433ad12bd4e34e50fac8f72668eac988eb2 (commit)
from b7c958992df0b2e9275c4df42133e2ebd50e1b8b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 78218433ad12bd4e34e50fac8f72668eac988eb2
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Apr 15 20:02:50 2023 +0200
core174: fix build of the u-boot initrd on aarch64
KVER was not defined so it has not build the initrd for u-boot.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/174/update.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/174/update.sh b/config/rootfiles/core/174/update.sh
index 25474a7b2..b18618dac 100644
--- a/config/rootfiles/core/174/update.sh
+++ b/config/rootfiles/core/174/update.sh
@@ -169,6 +169,7 @@ fi
# Rebuild initial ramdisk to apply microcode updates
dracut --regenerate-all --force
+KVER="xxxKVERxxx"
case "$(uname -m)" in
aarch64)
mkimage -A arm64 -T ramdisk -C lzma -d /boot/initramfs-${KVER}-ipfire.img /boot/uInit-${KVER}-ipfire
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-04-18 7:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4Q0wwh268Bz2xgF@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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