From: matt mooney <mfm@muteddisk.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RESEND PATCH 13/27] char: change to new flag variable
Date: Fri, 14 Jan 2011 06:12:36 -0800 [thread overview]
Message-ID: <a58843383b54133255c341e8988a09b74f8c1901.1295006565.git.mfm@muteddisk.com> (raw)
In-Reply-To: <cover.1295006561.git.mfm@muteddisk.com>
Replace EXTRA_CFLAGS with ccflags-y.
Signed-off-by: matt mooney <mfm@muteddisk.com>
Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
---
drivers/char/mwave/Makefile | 4 ++--
drivers/char/mwave/README | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/char/mwave/Makefile b/drivers/char/mwave/Makefile
index 26b4fce..efa6a82 100644
--- a/drivers/char/mwave/Makefile
+++ b/drivers/char/mwave/Makefile
@@ -9,7 +9,7 @@ obj-$(CONFIG_MWAVE) += mwave.o
mwave-y := mwavedd.o smapi.o tp3780i.o 3780i.o
# To have the mwave driver disable other uarts if necessary
-# EXTRA_CFLAGS += -DMWAVE_FUTZ_WITH_OTHER_DEVICES
+# ccflags-y := -DMWAVE_FUTZ_WITH_OTHER_DEVICES
# To compile in lots (~20 KiB) of run-time enablable printk()s for debugging:
-ccflags-y := -DMW_TRACE
+ccflags-y += -DMW_TRACE
diff --git a/drivers/char/mwave/README b/drivers/char/mwave/README
index 480251f..c2a58f4 100644
--- a/drivers/char/mwave/README
+++ b/drivers/char/mwave/README
@@ -11,7 +11,7 @@ are not saved by the BIOS and so do not persist after unload and reload.
0x0008 tp3780i tracing
Tracing only occurs if the driver has been compiled with the
- MW_TRACE macro #defined (i.e. let EXTRA_CFLAGS += -DMW_TRACE
+ MW_TRACE macro #defined (i.e. let ccflags-y := -DMW_TRACE
in the Makefile).
mwave_3780i_irq=5/7/10/11/15
--
1.7.3.4
next prev parent reply other threads:[~2011-01-14 14:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 14:12 [RESEND PATCH 00/27] update makefiles to use the newer flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 01/27] kernel: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 02/27] alpha: change to new flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 03/27] arm: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 04/27] h8300: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 05/27] ia64: change to new flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 06/27] m68k: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 07/27] microblaze: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 08/27] mips: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 09/27] s390: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 10/27] um: change to new flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 11/27] xtensa: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 12/27] fs: " matt mooney
2011-01-14 14:12 ` matt mooney [this message]
2011-01-14 14:12 ` [RESEND PATCH 14/27] dma: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 15/27] hwmon: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 16/27] ide: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 17/27] ieee802154: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 18/27] isdn: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 19/27] memstick: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 20/27] message: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 21/27] misc: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 22/27] net: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 23/27] pps: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 24/27] rapidio: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 25/27] rtc: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 26/27] scsi: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 27/27] video: " matt mooney
2011-03-17 13:15 ` [RESEND PATCH 00/27] update makefiles to use the newer flag variables Michal Marek
2011-03-17 13:19 ` Geert Uytterhoeven
2011-03-17 13:31 ` Michal Marek
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=a58843383b54133255c341e8988a09b74f8c1901.1295006565.git.mfm@muteddisk.com \
--to=mfm@muteddisk.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®