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. 7f841117c5377136b85c878fa7252e9a4458a526
Date: Wed, 08 Aug 2018 09:29:26 +0100	[thread overview]
Message-ID: <20180808082927.3DC1B1081BD5@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1415 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  7f841117c5377136b85c878fa7252e9a4458a526 (commit)
      from  07664187ac7323af8cbcce166be6fb5e6786fdca (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 7f841117c5377136b85c878fa7252e9a4458a526
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Wed Aug 8 10:26:38 2018 +0200

    kernel: fix build on x86_64
    
    oops i deleted a wrong line...
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Summary of changes:
 lfs/linux | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/linux b/lfs/linux
index cfdcc4a42..5e7b334cd 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -37,8 +37,9 @@ CXXFLAGS   =
 PAK_VER    = 76
 DEPS	   = ""
 
-KERNEL_TARGET = bzImage
 HEADERS_ARCH  = $(BUILD_PLATFORM)
+KERNEL_ARCH   = $(BUILD_ARCH)
+KERNEL_TARGET = bzImage
 
 ifeq "$(BUILD_ARCH)" "i586"
 	KERNEL_ARCH = i386


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

                 reply	other threads:[~2018-08-08  8:29 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=20180808082927.3DC1B1081BD5@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