From: Joe Perches <joe@perches.com>
To: Dave Young <dyoung@redhat.com>, linux-wireless@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, johannes@sipsolutions.net
Subject: Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages
Date: Sun, 15 Nov 2015 09:38:54 -0800 [thread overview]
Message-ID: <1447609134.6012.15.camel@perches.com> (raw)
In-Reply-To: <20151115073105.GA18846@dhcp-128-65.nay.redhat.com>
On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote:
> cfg80211 module prints a lot of messages like below. Actually printing
> once is acceptable but sometimes it will print again and again, it looks
> very annoying. It is better to change these detail messages to debugging
> only.
So maybe add some wrapper that does a pr_info then
a pr_debug for the second and subsequent uses like:
#define pr_info_once_then_debug(fmt, ...) \
({ \
static bool __print_once __read_mostly; \
\
if (!__print_once) { \
__print_once = true; \
pr_info(fmt, ##__VA_ARGS__); \
} else { \
pr_debug(fmt, ##__VA_ARGS__); \
} \
})
next prev parent reply other threads:[~2015-11-15 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 7:31 [PATCH] wireless: change cfg80211 regulatory domain info as debug messages Dave Young
2015-11-15 17:38 ` Joe Perches [this message]
2015-11-16 1:59 ` Dave Young
2015-11-16 10:38 ` Johannes Berg
2015-11-16 10:38 ` Johannes Berg
2015-11-15 18:25 ` Stefan Lippers-Hollmann
2015-11-16 1:58 ` Dave Young
2015-11-16 1:58 ` Dave Young
2015-11-20 11:55 ` Johannes Berg
2015-11-23 1:37 ` Dave Young
2015-12-11 14:26 ` Johannes Berg
2015-12-11 14:26 ` Johannes Berg
2015-12-17 3:19 ` Dave Young
2015-12-17 7:58 ` Johannes Berg
2015-12-11 14:38 ` Johannes Berg
2015-12-17 3:16 ` Dave Young
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=1447609134.6012.15.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=dyoung@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.