From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. ca666e151216fea6d1b5defcd926cad2b98cc145
Date: Thu, 19 Feb 2015 00:11:23 +0100 [thread overview]
Message-ID: <20150218231124.2956C21EE3@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3169 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, master has been updated
via ca666e151216fea6d1b5defcd926cad2b98cc145 (commit)
via 80e4980761a9ef222c278e048c059dee806584fa (commit)
from 741fa41c6ce99a23662ed90b174e6752732d91ad (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 ca666e151216fea6d1b5defcd926cad2b98cc145
Merge: 80e4980 741fa41
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Feb 19 00:11:13 2015 +0100
Merge branch 'master' of git.ipfire.org:/pub/git/ipfire-2.x
commit 80e4980761a9ef222c278e048c059dee806584fa
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Feb 19 00:10:33 2015 +0100
kernel: update to 3.14.33.
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 19 ++++++++-----------
1 file changed, 8 insertions(+), 11 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index d92bdfe..4e6e9ec 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,11 +24,11 @@
include Config
-VER = 3.14.32
+VER = 3.14.33
-RPI_PATCHES = 3.14.32-grsec-ipfire1
-A7M_PATCHES = 3.14.32-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.0-3.14.32-201502062101.patch.xz
+RPI_PATCHES = 3.14.33-grsec-ipfire1
+A7M_PATCHES = 3.14.33-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.0-3.14.33-201502180832.patch.xz
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -77,10 +77,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 = 3178fb8f6f1eafcffdd730fec68754f8
-rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 375dc501711ff3ffeffdfc9848675d26
-arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = efcfe5889f120d879387dd4ebe881587
-$(GRS_PATCHES)_MD5 = c1565eb2a630a673f3ace31a6901e251
+$(DL_FILE)_MD5 = c19feb0646fde7e96602ac313fb7e5d6
+rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = e423c8b3a408f23b9a26f8f0f4384c50
+arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = f147ce7c81889d2c5134304f3a6e60e3
+$(GRS_PATCHES)_MD5 = 119943451628ff5a62437637d60a585d
install : $(TARGET)
@@ -175,9 +175,6 @@ ifeq "$(KCFG)" "-multi"
# Apply Arm7-multiarch kernel patches.
cd $(DIR_APP) && xzcat $(DIR_DL)/arm7-multi-patches-$(A7M_PATCHES).patch.xz | patch -Np1
- # Update Banana Pi, Lamobo-R1 and add Banana Pro dtb
- cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-3.14.x-update_banana_dts.patch
-
# Install switch api userspace header
cd $(DIR_APP) && install -v -m644 include/uapi/linux/switch.h /usr/include/linux/
endif
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-02-18 23:11 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=20150218231124.2956C21EE3@argus.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