From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 6d3a3709d4766a98ffc6379ebf5b13a6627a9387
Date: Tue, 19 May 2026 07:16:13 +0000 (UTC) [thread overview]
Message-ID: <4gKQvK1zCMz2xKy@people01.haj.ipfire.org> (raw)
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 6d3a3709d4766a98ffc6379ebf5b13a6627a9387 (commit)
from 0a634bf539610d9aa6e4e974c65bec853116c5f1 (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 6d3a3709d4766a98ffc6379ebf5b13a6627a9387
Author: Arne Fitzenreiter <arne_f@ipfire.org>
Date: Tue May 19 09:13:20 2026 +0200
kernel: update to 6.18.32
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/kernel/kernel.config.x86_64-ipfire | 2 +-
lfs/linux | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
index b5ab100b5..36345ca47 100644
--- a/config/kernel/kernel.config.x86_64-ipfire
+++ b/config/kernel/kernel.config.x86_64-ipfire
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# Linux/x86 6.18.28 Kernel Configuration
+# Linux/x86 6.18.32 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 15.2.0"
CONFIG_CC_IS_GCC=y
diff --git a/lfs/linux b/lfs/linux
index e27a366f5..0ece11f46 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,7 +24,7 @@
include Config
-VER = 6.18.28
+VER = 6.18.32
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -69,7 +69,7 @@ objects = \
$(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 3684278c2d75e87c0083424ccfd6917518d3e28f5a94db9fa33a7787f8e7aa836453547218e2b466b02adf73135f28d84ebf39f0b58f145179d23cd53bb0c8f3
+$(DL_FILE)_BLAKE2 = f292fd58cf61b23dbe40e4a1124d2e310712b2b3826195f348b9c5ab7773de9b4eed48e9abc524c5c2d5a05adab13fd305bab7ebfa0a829217e265ff4cdc69f5
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-19 7:16 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=4gKQvK1zCMz2xKy@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