Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: <linux-wireless@vger.kernel.org>
Cc: <hauke@hauke-m.de>, <nbd@nbd.name>, <linville@tuxdriver.com>,
	"Luis R. Rodriguez" <mcgrof@frijolero.org>
Subject: [PATCH 3/5] compat-wireless: fix old checks on KERNEL_SUBLEVEL
Date: Fri, 24 Feb 2012 17:52:04 -0800	[thread overview]
Message-ID: <1330134726-1634-4-git-send-email-rodrigue@qca.qualcomm.com> (raw)
In-Reply-To: <1330134726-1634-1-git-send-email-rodrigue@qca.qualcomm.com>

From: Luis R. Rodriguez <mcgrof@frijolero.org>

KERNEL_SUBLEVEL used to be used on config.mk for th 2.6.x series
but after 3.x support was added the variable should have been
changed to KERNEL_26SUBLEVEL.

Signed-off-by: Luis R. Rodriguez <mcgrof@frijolero.org>
---
 config.mk |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/config.mk b/config.mk
index f8a4ca5..4b47321 100644
--- a/config.mk
+++ b/config.mk
@@ -53,7 +53,8 @@ endif
 # 2.6.27 has FTRACE_DYNAMIC borked, so we will complain if
 # you have it enabled, otherwise you will very likely run into
 # a kernel panic.
-ifeq ($(shell test $(KERNEL_VERSION) -eq 2 -a $(KERNEL_SUBLEVEL) -eq 27 && echo yes),yes)
+# XXX: move this to compat_autoconf.h script generation
+ifeq ($(shell test $(KERNEL_VERSION) -eq 2 -a $(KERNEL_26SUBLEVEL) -eq 27 && echo yes),yes)
 ifeq ($(CONFIG_DYNAMIC_FTRACE),y)
 $(error "ERROR: Your 2.6.27 kernel has CONFIG_DYNAMIC_FTRACE, please upgrade your distribution kernel as newer ones should not have this enabled (and if so report a bug) or remove this warning if you know what you are doing")
 endif
@@ -70,7 +71,8 @@ endif
 #
 # In kernel 2.6.32 both attributes were removed.
 #
-ifeq ($(shell test $(KERNEL_VERSION) -eq 2 -a $(KERNEL_SUBLEVEL) -ge 27 -a $(KERNEL_SUBLEVEL) -le 31 && echo yes),yes)
+# XXX: move this to compat_autoconf.h script generation
+ifeq ($(shell test $(KERNEL_VERSION) -eq 2 -a $(KERNEL_26SUBLEVEL) -ge 27 -a $(KERNEL_26SUBLEVEL) -le 31 && echo yes),yes)
 ifeq ($(CONFIG_MAC80211),)
 $(error "ERROR: Your >=2.6.27 and <= 2.6.31 kernel has CONFIG_MAC80211 disabled, you should have it CONFIG_MAC80211=m if you want to use this thing.")
 endif
-- 
1.7.4.15.g7811d


  parent reply	other threads:[~2012-02-25  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25  1:52 [PATCH 0/5] compat / compat-wireless: merge autoconf generation Luis R. Rodriguez
2012-02-25  1:52 ` [PATCH 1/5] compat: fix few compilations by adding compat_autoconf.h support Luis R. Rodriguez
2012-02-25  1:52 ` [PATCH 2/5] compat: add some initial RHEL support Luis R. Rodriguez
2012-02-25  1:52 ` Luis R. Rodriguez [this message]
2012-02-25  1:52 ` [PATCH 4/5] compat-wireless: start using CONFIG_COMPAT_KERNEL_ in code Luis R. Rodriguez
2012-02-25  1:52 ` [PATCH 5/5] compat-wireless: use compat's CONFIG_COMPAT_KERNEL_* variables Luis R. Rodriguez
2012-02-25 11:05 ` [PATCH 0/5] compat / compat-wireless: merge autoconf generation Hauke Mehrtens
2012-02-27 21:18   ` 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=1330134726-1634-4-git-send-email-rodrigue@qca.qualcomm.com \
    --to=rodrigue@qca.qualcomm.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@frijolero.org \
    --cc=nbd@nbd.name \
    /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