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, core124, updated. eaadeb5af0173e4ed4067a650beb3802a417ca20
Date: Thu, 27 Sep 2018 07:05:50 +0100	[thread overview]
Message-ID: <20180927060551.CB50D1081BD3@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2138 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, core124 has been updated
       via  eaadeb5af0173e4ed4067a650beb3802a417ca20 (commit)
      from  161a5b834a7bdc134996c0d24a642242f42fcc2c (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 eaadeb5af0173e4ed4067a650beb3802a417ca20
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Sep 27 08:03:45 2018 +0200

    kernel: update to 4.14.72
    
    this commit has many important driver updates so we need to ship it fast...
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Summary of changes:
 lfs/linux | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

Difference in files:
diff --git a/lfs/linux b/lfs/linux
index ad10bc8e5..814bc0b73 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
 
 include Config
 
-VER         = 4.14.71
-ARM_PATCHES = 4.14.71-ipfire0
+VER         = 4.14.72
+ARM_PATCHES = 4.14.72-ipfire0
 
 THISAPP    = linux-$(VER)
 DL_FILE    = linux-$(VER).tar.xz
@@ -34,7 +34,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 CFLAGS     =
 CXXFLAGS   =
 
-PAK_VER    = 77
+PAK_VER    = 78
 DEPS	   = ""
 
 HEADERS_ARCH  = $(BUILD_PLATFORM)
@@ -82,10 +82,9 @@ 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					= 14b21e5f11e8e195731c89a14794a0fc
+$(DL_FILE)_MD5					= 450b3f5f1124442dee768eaa097fd149
 arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5	= 889a8d49a63bf462067409887f8105bb
 
-
 install : $(TARGET)
 
 check : $(patsubst %,$(DIR_CHK)/%,$(objects))


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

                 reply	other threads:[~2018-09-27  6:05 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=20180927060551.CB50D1081BD3@git01.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