public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1b8327f50e2d4daf7860bc39a864c1bdeea0a4ae
Date: Thu, 20 Feb 2014 23:38:35 +0100	[thread overview]
Message-ID: <20140220223836.5EF0320838@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2852 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  1b8327f50e2d4daf7860bc39a864c1bdeea0a4ae (commit)
      from  cc21b588df77bfc807720c1456f901614e98e382 (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 1b8327f50e2d4daf7860bc39a864c1bdeea0a4ae
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Feb 20 23:37:22 2014 +0100

    kernel: update to 3.10.31.

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

Summary of changes:
 config/rootfiles/common/i586/linux |  1 +
 lfs/linux                          | 10 +++++-----
 2 files changed, 6 insertions(+), 5 deletions(-)

Difference in files:
diff --git a/config/rootfiles/common/i586/linux b/config/rootfiles/common/i586/linux
index 3ec81ec..1a08e17 100644
--- a/config/rootfiles/common/i586/linux
+++ b/config/rootfiles/common/i586/linux
@@ -1879,6 +1879,7 @@ lib/modules/KVER-ipfire
 #lib/modules/KVER-ipfire/kernel/drivers/scsi/hpsa.ko
 #lib/modules/KVER-ipfire/kernel/drivers/scsi/hptiop.ko
 #lib/modules/KVER-ipfire/kernel/drivers/scsi/hv_storvsc.ko
+#lib/modules/KVER-ipfire/kernel/drivers/scsi/imm.ko
 #lib/modules/KVER-ipfire/kernel/drivers/scsi/in2000.ko
 #lib/modules/KVER-ipfire/kernel/drivers/scsi/initio.ko
 #lib/modules/KVER-ipfire/kernel/drivers/scsi/ipr.ko
diff --git a/lfs/linux b/lfs/linux
index d460708..0bbfa10 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
 
 include Config
 
-VER        = 3.10.30
+VER        = 3.10.31
 
 RPI_PATCHES = linux-3.10.27-grsec-943b563
-GRS_PATCHES = grsecurity-2.9.1-3.10.30-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.31-ipfire1.patch.xz
 
 THISAPP    = linux-$(VER)
 DL_FILE    = linux-$(VER).tar.xz
@@ -36,7 +36,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 CFLAGS     =
 CXXFLAGS   =
 
-PAK_VER    = 35
+PAK_VER    = 36
 DEPS	   = ""
 
 VERSUFIX=ipfire$(KCFG)
@@ -74,9 +74,9 @@ $(DL_FILE)				= $(URL_IPFIRE)/$(DL_FILE)
 rpi-patches-$(RPI_PATCHES).patch.xz	= $(URL_IPFIRE)/rpi-patches-$(RPI_PATCHES).patch.xz
 $(GRS_PATCHES)				= $(URL_IPFIRE)/$(GRS_PATCHES)
 
-$(DL_FILE)_MD5				= f48ca7dd9f2eb14a2903cb6a4fbe07ed
+$(DL_FILE)_MD5				= 19e2b31f6883822ef35b974813e8e98e
 rpi-patches-$(RPI_PATCHES).patch.xz_MD5	= 8cf81f48408306d93ccee59b58af2e92
-$(GRS_PATCHES)_MD5			= 044e29280d4717441e89e8d80abba563
+$(GRS_PATCHES)_MD5			= ac71d9a1a5b7fabeb76ddef95518acd0
 
 install : $(TARGET)
 


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

                 reply	other threads:[~2014-02-20 22:38 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=20140220223836.5EF0320838@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