summaryrefslogtreecommitdiff
path: root/net/dccp
diff options
context:
space:
mode:
authorGerrit Renker <gerrit@erg.abdn.ac.uk>2007-03-20 17:59:23 (GMT)
committerDavid S. Miller <davem@sunset.davemloft.net>2007-04-26 05:26:53 (GMT)
commitac12b0c49571fe4c3a2f4957ed494da316d558be (patch)
tree47f6b91bb2c36f954800ae795344288ee3755a9a /net/dccp
parent1266adee12d25385a25e1c57b1e3ff05a90bb4d7 (diff)
downloadlinux-fsl-qoriq-ac12b0c49571fe4c3a2f4957ed494da316d558be.tar.xz
[DCCP]: Always use debug-toggle parameters
Currently debugging output (when configured) is automatically enabled when DCCP modules are compiled into the kernel rather than built as loadable modules. This is not necessary, since the module parameters in this case become kernel commandline parameters, e.g. DCCP or CCID3 debug output can be enabled for a static build by appending the following at the boot prompt: dccp.dccp_debug=1 dccp_ccid3.ccid3_debug=1 This patch therefore does away with the more complicated way of always enabling debug output for static builds Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/dccp')
-rw-r--r--net/dccp/dccp.h4
1 files changed, 0 insertions, 4 deletions
diff --git a/net/dccp/dccp.h b/net/dccp/dccp.h
index c66a458..292f18e 100644
--- a/net/dccp/dccp.h
+++ b/net/dccp/dccp.h
@@ -31,13 +31,9 @@
__stringify(cond)); \
} while (0)
-#ifdef MODULE
#define DCCP_PRINTK(enable, fmt, args...) do { if (enable) \
printk(fmt, ##args); \
} while(0)
-#else
-#define DCCP_PRINTK(enable, fmt, args...) printk(fmt, ##args)
-#endif
#define DCCP_PR_DEBUG(enable, fmt, a...) DCCP_PRINTK(enable, KERN_DEBUG \
"%s: " fmt, __FUNCTION__, ##a)