From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core104, updated. 66cb9ec42bba14237972f3e7e4532eb1d936100d
Date: Sun, 21 Aug 2016 17:03:13 +0100 [thread overview]
Message-ID: <20160821160313.E4B931081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2658 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, core104 has been updated
via 66cb9ec42bba14237972f3e7e4532eb1d936100d (commit)
from 2a78041a3f28f93a84f74fdcace99aa44bbf92b1 (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 66cb9ec42bba14237972f3e7e4532eb1d936100d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Aug 21 17:56:47 2016 +0200
kernel: update to 3.14.77
fix performance issue with tcp ack security fix.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index cfea069..5c37a4b 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.14.76
-RPI_PATCHES = 3.14.76-grsec-ipfire1
-A7M_PATCHES = 3.14.76-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.1ipfire-3.14.76-v1.patch.xz
+VER = 3.14.77
+RPI_PATCHES = 3.14.77-grsec-ipfire1
+A7M_PATCHES = 3.14.77-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.1ipfire-3.14.77-v1.patch.xz
THISAPP = linux-$(VER)
@@ -37,7 +37,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
CFLAGS =
CXXFLAGS =
-PAK_VER = 70
+PAK_VER = 71
DEPS = ""
KERNEL_ARCH = $(MACHINE)
@@ -83,10 +83,10 @@ rpi-patches-$(RPI_PATCHES).patch.xz = $(URL_IPFIRE)/rpi-patches-$(RPI_PATCHES).
arm7-multi-patches-$(A7M_PATCHES).patch.xz = $(URL_IPFIRE)/arm7-multi-patches-$(A7M_PATCHES).patch.xz
$(GRS_PATCHES) = $(URL_IPFIRE)/$(GRS_PATCHES)
-$(DL_FILE)_MD5 = 1624610ba8a7b83e8be73cee58a5ca5b
-rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 4a7b9c86a565662e2c340086c0c20fa4
-arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = 873a8d057dbf850693e695df778d608c
-$(GRS_PATCHES)_MD5 = e45c8c839449672fa607ad7b59ccc5c7
+$(DL_FILE)_MD5 = 7ecb8518498d0666a7b88f359e566f4c
+rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 3213020a9627ea73cc9668e2db4ff8a4
+arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = 56949a37637656d5ea23658cc9222f64
+$(GRS_PATCHES)_MD5 = 5ed67f97c3b0de1b290f9155eb166c56
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-08-21 16:03 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=20160821160313.E4B931081BA6@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