From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, seventeen, updated. cee50e12f6b9a1a0915ad8a2db80b3365f55d3ba
Date: Thu, 27 Nov 2014 07:58:25 +0100 [thread overview]
Message-ID: <20141127065826.3292521A61@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1690 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, seventeen has been updated
via cee50e12f6b9a1a0915ad8a2db80b3365f55d3ba (commit)
from e40740b2e2111177ceee12529a18476ca83cb155 (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 cee50e12f6b9a1a0915ad8a2db80b3365f55d3ba
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Nov 27 07:57:54 2014 +0100
kernel: fix build.
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 2e8a558..7e7714f 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -176,6 +176,7 @@ ifeq "$(KCFG)" "-rpi"
cd $(DIR_APP) && xzcat $(DIR_DL)/rpi-patches-$(RPI_PATCHES).patch.xz | patch -Np1
endif
+ifeq "$(KCFG)" "-headers"
# Install the header files
cd $(DIR_APP) && make ARCH=$(HEADERS_ARCH) INSTALL_HDR_PATH=dest headers_install
-mkdir -pv $(BUILDROOT)/$(HEADERS_PREFIX)/include
@@ -252,6 +253,7 @@ ifeq "$(LASTKERNEL)" "1"
echo "options ipv6 disable_ipv6=1" > /etc/modprobe.d/ipv6.conf
endif
endif
+endif
#force new build of external modules and initrd if the kernel was rebuild
-rm -f /usr/src/log/*-kmod-$(VER)-$(VERSUFIX)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-11-27 6:58 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=20141127065826.3292521A61@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