From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 07664187ac7323af8cbcce166be6fb5e6786fdca
Date: Tue, 07 Aug 2018 18:06:39 +0100 [thread overview]
Message-ID: <20180807170640.8EF231081BD5@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1446 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 07664187ac7323af8cbcce166be6fb5e6786fdca (commit)
from 7529349754e0f99f626a36c895347806fc6f2dd2 (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 07664187ac7323af8cbcce166be6fb5e6786fdca
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Aug 7 19:05:35 2018 +0200
kernel: fix build on armv5tel
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index b5877fc5b..cfdcc4a42 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -37,7 +37,6 @@ CXXFLAGS =
PAK_VER = 76
DEPS = ""
-KERNEL_ARCH = $(BUILD_ARCH)
KERNEL_TARGET = bzImage
HEADERS_ARCH = $(BUILD_PLATFORM)
@@ -52,6 +51,7 @@ ifeq "$(BUILD_ARCH)" "aarch64"
endif
ifeq "$(BUILD_ARCH)" "armv5tel"
+ KERNEL_ARCH = arm
KERNEL_TARGET = zImage
endif
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-08-07 17:06 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=20180807170640.8EF231081BD5@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