From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6581c6e3a6c28e040c2bbaae21f1f5c926d4b840
Date: Fri, 22 Mar 2024 10:59:17 +0000 [thread overview]
Message-ID: <4V1K8Q0H1Yz2xft@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 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 6581c6e3a6c28e040c2bbaae21f1f5c926d4b840 (commit)
from 790c04a6eaafcf695315dcd3f4f39ec6b35be48c (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 6581c6e3a6c28e040c2bbaae21f1f5c926d4b840
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Mar 22 11:58:49 2024 +0100
kernel: update aarch64 rootfile
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/aarch64/linux | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/common/aarch64/linux b/config/rootfiles/common/aarch64/linux
index 3dcacfd4d..57c93f242 100644
--- a/config/rootfiles/common/aarch64/linux
+++ b/config/rootfiles/common/aarch64/linux
@@ -23220,6 +23220,7 @@ lib/modules/KVER-ipfire/modules.symbols.bin
sbin/gen_init_cpio
#usr/bin/cpufreq-bench_plot.sh
usr/bin/cpupower
+#usr/include/cpufreq.h
#usr/include/cpuidle.h
#usr/include/powercap.h
#usr/lib/libcpupower.so
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-03-22 10:59 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=4V1K8Q0H1Yz2xft@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