From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b7a46724970feeb1edd11bc779db1ca53da0ccdb
Date: Thu, 17 May 2018 07:13:40 +0100 [thread overview]
Message-ID: <20180517061341.1CC071081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2657 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 b7a46724970feeb1edd11bc779db1ca53da0ccdb (commit)
from 4dd7df2f82266d8d7a4474568020a326e9823f40 (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 b7a46724970feeb1edd11bc779db1ca53da0ccdb
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu May 17 07:45:06 2018 +0200
kernel: update to 4.14.41
Signen-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/armv5tel/linux-multi | 1 +
lfs/linux | 8 ++++----
2 files changed, 5 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/armv5tel/linux-multi b/config/rootfiles/common/armv5tel/linux-multi
index 1b6139c6b..94838e119 100644
--- a/config/rootfiles/common/armv5tel/linux-multi
+++ b/config/rootfiles/common/armv5tel/linux-multi
@@ -86,6 +86,7 @@ boot/dtb-KVER-ipfire-multi
#boot/dtb-KVER-ipfire-multi/bcm2835-rpi-zero-w.dtb
#boot/dtb-KVER-ipfire-multi/bcm2835-rpi-zero.dtb
#boot/dtb-KVER-ipfire-multi/bcm2836-rpi-2-b.dtb
+#boot/dtb-KVER-ipfire-multi/bcm2837-rpi-3-b-plus.dtb
#boot/dtb-KVER-ipfire-multi/bcm2837-rpi-3-b.dtb
#boot/dtb-KVER-ipfire-multi/berlin2-sony-nsz-gs7.dtb
#boot/dtb-KVER-ipfire-multi/berlin2cd-google-chromecast.dtb
diff --git a/lfs/linux b/lfs/linux
index 5db41c434..3ae2a8764 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 4.14.40
-ARM_PATCHES = 4.14.40-ipfire0
+VER = 4.14.41
+ARM_PATCHES = 4.14.41-ipfire0
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -75,8 +75,8 @@ 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 = 8376ed89777760443a359edb1d08ed9a
-arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = ae7091bb79bad05c8394c8bacc48dd60
+$(DL_FILE)_MD5 = ce212dfed5c5e8a92808f675ef433382
+arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 12f346d38b519c71d9e9837529d53494
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-05-17 6:13 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=20180517061341.1CC071081DF2@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