From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5380ebc7c3443a5529f98a89bb66346327412237
Date: Wed, 20 Nov 2024 12:51:09 +0000 [thread overview]
Message-ID: <4Xth7K4PXlz2xP0@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2236 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, next has been updated
via 5380ebc7c3443a5529f98a89bb66346327412237 (commit)
from c3d1de3ee83c8f7748c6efc43d77fef4c0c82aed (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 5380ebc7c3443a5529f98a89bb66346327412237
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Nov 20 15:51:39 2024 +0100
kernel: rootfile update aarch64
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/aarch64/linux | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/aarch64/linux b/config/rootfiles/common/aarch64/linux
index a65a2d7a1..18064d079 100644
--- a/config/rootfiles/common/aarch64/linux
+++ b/config/rootfiles/common/aarch64/linux
@@ -346,6 +346,8 @@ boot/dtb-KVER
#boot/dtb-KVER/rockchip/rk3328-nanopi-r2c-plus.dtb
#boot/dtb-KVER/rockchip/rk3328-nanopi-r2c.dtb
#boot/dtb-KVER/rockchip/rk3328-nanopi-r2s-oc.dtb
+#boot/dtb-KVER/rockchip/rk3328-nanopi-r2s-plus-oc.dtb
+#boot/dtb-KVER/rockchip/rk3328-nanopi-r2s-plus.dtb
#boot/dtb-KVER/rockchip/rk3328-nanopi-r2s.dtb
#boot/dtb-KVER/rockchip/rk3328-orangepi-r1-plus-lts-oc.dtb
#boot/dtb-KVER/rockchip/rk3328-orangepi-r1-plus-lts.dtb
@@ -7286,7 +7288,6 @@ etc/modprobe.d/ipv6.conf
#lib/modules/KVER/build/include/config/ARM64_PTR_AUTH
#lib/modules/KVER/build/include/config/ARM64_PTR_AUTH_KERNEL
#lib/modules/KVER/build/include/config/ARM64_RAS_EXTN
-#lib/modules/KVER/build/include/config/ARM64_SME
#lib/modules/KVER/build/include/config/ARM64_SVE
#lib/modules/KVER/build/include/config/ARM64_SW_TTBR0_PAN
#lib/modules/KVER/build/include/config/ARM64_TAGGED_ADDR_ABI
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-11-20 12:51 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=4Xth7K4PXlz2xP0@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