public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 79930b29a4cf0e891c294c3a1db22b0d7c0a03f1
Date: Fri, 15 Oct 2021 06:07:33 +0000	[thread overview]
Message-ID: <4HVwm55NZLz2xbc@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2880 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  79930b29a4cf0e891c294c3a1db22b0d7c0a03f1 (commit)
      from  b04724fd348c2f4e41607603ab25c1f18b96a919 (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 79930b29a4cf0e891c294c3a1db22b0d7c0a03f1
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Oct 15 08:07:04 2021 +0200

    kernel: update to 5.10.73
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/kernel/kernel.config.i586-ipfire   | 2 +-
 config/kernel/kernel.config.x86_64-ipfire | 2 +-
 lfs/linux                                 | 6 +++---
 3 files changed, 5 insertions(+), 5 deletions(-)

Difference in files:
diff --git a/config/kernel/kernel.config.i586-ipfire b/config/kernel/kernel.config.i586-ipfire
index f3732effc..179247fa2 100644
--- a/config/kernel/kernel.config.i586-ipfire
+++ b/config/kernel/kernel.config.i586-ipfire
@@ -1,6 +1,6 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/x86 5.10.72-ipfire Kernel Configuration
+# Linux/x86 5.10.73-ipfire Kernel Configuration
 #
 CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.1.0"
 CONFIG_CC_IS_GCC=y
diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
index 4d2953c62..e7337f2a3 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.72-ipfire Kernel Configuration
+# Linux/x86 5.10.73-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 0ab3fbb20..366c894c0 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
 
 include Config
 
-VER         = 5.10.72
-ARM_PATCHES = 5.10.72-ipfire1
+VER         = 5.10.73
+ARM_PATCHES = 5.10.73-ipfire1
 
 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					= d13044e4fccf0ca95ec42e9d5a5d3923
+$(DL_FILE)_MD5					= 2ce35f58bce3ebdcead1e0eec6fb7dd2
 arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5	= 02a75302a5b4a157e3d67ae62af6b178
 
 install : $(TARGET)


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2021-10-15  6:07 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=4HVwm55NZLz2xbc@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