From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>,
Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Subject: Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages
Date: Mon, 16 Nov 2015 11:38:05 +0100 [thread overview]
Message-ID: <1447670285.2417.9.camel@sipsolutions.net> (raw)
In-Reply-To: <1447609134.6012.15.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
> So maybe add some wrapper that does a pr_info then
> a pr_debug for the second and subsequent uses like:
>
That seems like a bad idea - one might be tricked into think that one
saw the current data, but the actually current data is later hidden.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-11-16 10:38 UTC|newest]
Thread overview: 13+ 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
2015-11-16 1:59 ` Dave Young
[not found] ` <1447609134.6012.15.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2015-11-16 10:38 ` Johannes Berg [this message]
2015-11-15 18:25 ` Stefan Lippers-Hollmann
2015-11-16 1:58 ` Dave Young
2015-11-20 11:55 ` Johannes Berg
2015-11-23 1:37 ` Dave Young
[not found] ` <20151123013740.GA27383-0VdLhd/A9PnLJg/3yGtlgR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
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=1447670285.2417.9.camel@sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).