From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 542edad66e46b160cdb2967bff2a0bea2fb48586
Date: Mon, 19 Jul 2021 12:27:28 +0000 [thread overview]
Message-ID: <4GT1M46xN3z2y2p@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2367 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 542edad66e46b160cdb2967bff2a0bea2fb48586 (commit)
from 93f83a3f0d7ecaed22675bb47f33c74dc994b52b (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 542edad66e46b160cdb2967bff2a0bea2fb48586
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Jul 19 14:08:08 2021 +0200
kernel: update to 5.10.51
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/kernel/kernel.config.x86_64-ipfire | 2 +-
lfs/linux | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
index a156b8abb..15bc77545 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 5.10.50-ipfire Kernel Configuration
+# Linux/x86 5.10.51-ipfire Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.1.0"
CONFIG_CC_IS_GCC=y
diff --git a/lfs/linux b/lfs/linux
index b891c5511..1d1032ea0 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 5.10.50
-ARM_PATCHES = 5.10.50-ipfire0
+VER = 5.10.51
+ARM_PATCHES = 5.10.51-ipfire0
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -77,7 +77,7 @@ objects =$(DL_FILE) \
$(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
arm-multi-patches-$(ARM_PATCHES).patch.xz = $(URL_IPFIRE)/arm-multi-patches-$(ARM_PATCHES).patch.xz
-$(DL_FILE)_MD5 = 8df73961d6e477b08d5b6d96e1c9929f
+$(DL_FILE)_MD5 = e317f85fc9641b4f92b386b2fcf4b599
arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 1b66be2d80c102c6c1963e9f601e5099
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-07-19 12:27 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=4GT1M46xN3z2y2p@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