netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Hansjoerg Lipp <hjlipp@web.de>,
	Karsten Keil <isdn@linux-pingi.de>,
	Karsten Keil <keil@b1-systems.de>,
	isdn4linux@listserv.isdn4linux.de,
	i4ldeveloper@listserv.isdn4linux.de
Subject: [PATCH 04/11] gigaset: announce if built with debugging
Date: Wed,  7 Oct 2009 00:18:41 +0200 (CEST)	[thread overview]
Message-ID: <20091006-patch-gigaset-04.tilman@imap.cc> (raw)
In-Reply-To: <20091006-patch-gigaset-00.tilman@imap.cc>

Mention in the driver load announcement whether the driver was built
with debugging messages enabled, to facilitate support.

Impact: informational message
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
---
 drivers/isdn/gigaset/common.c |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/drivers/isdn/gigaset/common.c b/drivers/isdn/gigaset/common.c
index e4141bf..edbcaa3 100644
--- a/drivers/isdn/gigaset/common.c
+++ b/drivers/isdn/gigaset/common.c
@@ -22,6 +22,12 @@
 #define DRIVER_AUTHOR "Hansjoerg Lipp <hjlipp@web.de>, Tilman Schmidt <tilman@imap.cc>, Stefan Eilers"
 #define DRIVER_DESC "Driver for Gigaset 307x"
 
+#ifdef CONFIG_GIGASET_DEBUG
+#define DRIVER_DESC_DEBUG " (debug build)"
+#else
+#define DRIVER_DESC_DEBUG ""
+#endif
+
 /* Module parameters */
 int gigaset_debuglevel = DEBUG_DEFAULT;
 EXPORT_SYMBOL_GPL(gigaset_debuglevel);
@@ -1110,7 +1116,7 @@ static int __init gigaset_init_module(void)
 	if (gigaset_debuglevel == 1)
 		gigaset_debuglevel = DEBUG_DEFAULT;
 
-	pr_info(DRIVER_DESC "\n");
+	pr_info(DRIVER_DESC DRIVER_DESC_DEBUG "\n");
 	return 0;
 }
 
-- 
1.6.2.1.214.ge986c

  parent reply	other threads:[~2009-10-06 22:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 22:18 [PATCH 00/11] Gigaset driver patches for 2.6.32 (v3) Tilman Schmidt
2009-10-06 22:18 ` [PATCH 01/11] gigaset: fix reject/hangup handling Tilman Schmidt
2009-10-06 22:18 ` [PATCH 02/11] gigaset: linearize skb Tilman Schmidt
2009-10-06 22:18 ` [PATCH 03/11] gigaset: handle isoc frame errors more gracefully Tilman Schmidt
2009-10-06 22:18 ` Tilman Schmidt [this message]
2009-10-06 22:18 ` [PATCH 05/11] gigaset: fix device ERROR response handling Tilman Schmidt
2009-10-06 22:19 ` [PATCH 08/11] gigaset: add kerneldoc comments Tilman Schmidt
     [not found] ` <20091006-patch-gigaset-00.tilman-ZTO5kqT2PaM@public.gmane.org>
2009-10-06 22:18   ` [PATCH 06/11] gigaset: improve error recovery Tilman Schmidt
2009-10-06 22:18   ` [PATCH 07/11] gigaset: correct debugging output selection Tilman Schmidt
2009-10-06 22:19   ` [PATCH 09/11] gigaset: prepare for CAPI implementation Tilman Schmidt
2009-10-06 22:19   ` [PATCH 11/11] gigaset: add Kernel CAPI interface (v3) Tilman Schmidt
2009-10-07  6:39   ` [PATCH 00/11] Gigaset driver patches for 2.6.32 (v3) David Miller
     [not found]     ` <1254904188.9411@nb-hp>
2009-10-07  8:30       ` David Miller
2009-10-06 22:19 ` [PATCH 10/11] gigaset: allow building without I4L Tilman Schmidt

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=20091006-patch-gigaset-04.tilman@imap.cc \
    --to=tilman@imap.cc \
    --cc=davem@davemloft.net \
    --cc=hjlipp@web.de \
    --cc=i4ldeveloper@listserv.isdn4linux.de \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=isdn@linux-pingi.de \
    --cc=keil@b1-systems.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).