linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: [PATCH 1/2] compat-wireless: include config.mk early
Date: Fri, 30 Mar 2012 13:11:04 +0200	[thread overview]
Message-ID: <1333105864.3908.12.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1333105815.3908.11.camel@jlt3.sipsolutions.net> (sfid-20120330_131022_444171_B95DE05C)

From: Johannes Berg <johannes.berg@intel.com>

Not doing so can cause extreme build slowdowns,
somehow that confuses the kernel's Makefiles into
calculating the size of every single file all the
time (the calculation code is part of compressing
the kernel with bzip2 etc. so that's very strange.)

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
 Makefile |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/Makefile b/Makefile
index 67f8e84..bbd77f7 100644
--- a/Makefile
+++ b/Makefile
@@ -12,7 +12,6 @@ DESTDIR?=
 
 ifneq ($(KERNELRELEASE),)
 
-include $(COMPAT_CONFIG_CW)
 include $(COMPAT_CONFIG)
 
 NOSTDINC_FLAGS := -I$(M)/include/ \
@@ -68,6 +67,8 @@ export COMPAT_AUTOCONF=include/linux/compat_autoconf.h
 export CREL_PRE:=.compat_autoconf_
 export CREL_CHECK:=$(PWD)/$(CREL_PRE)$(CREL)
 
+include $(COMPAT_CONFIG_CW)
+
 all: modules
 
 $(COMPAT_CONFIG): ;
-- 
1.7.9.1




  reply	other threads:[~2012-03-30 11:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 11:10 [PATCH 0/2] compat: fix extreme build slowdowns Johannes Berg
2012-03-30 11:11 ` Johannes Berg [this message]
2012-03-30 11:11 ` [PATCH 2/2] compat: explicitly export generated variables Johannes Berg
2012-03-30 20:30   ` Luis R. Rodriguez
2012-03-30 20:34     ` Johannes Berg
2012-03-30 20:38       ` Luis R. Rodriguez
2012-03-30 11:26 ` [PATCH 0/2] compat: fix extreme build slowdowns Sujith Manoharan
2012-03-30 11:30   ` Johannes Berg
2012-03-30 14:41     ` Richard Farina
2012-03-30 20:43       ` Luis R. Rodriguez
2012-03-30 21:24         ` Luis R. Rodriguez
2012-03-30 21:48           ` Luis R. Rodriguez
2012-03-31  9:24             ` Luis R. Rodriguez

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=1333105864.3908.12.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).