From: "Zhao\, Gang" <gamerh2o@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Christian Lamparter <chunkeey@googlemail.com>
Subject: Re: [PATCH 1/6] p54: replace wiphy_debug() with wiphy_dbg()
Date: Fri, 18 Apr 2014 15:48:57 +0800 [thread overview]
Message-ID: <87ppkf5b86.fsf@gmail.com> (raw)
In-Reply-To: <1397754900.3104.5.camel@joe-AO725> (Joe Perches's message of "Thu, 17 Apr 2014 10:15:00 -0700")
On Thu, 2014-04-17 at 10:15:00 -0700, Joe Perches wrote:
> On Thu, 2014-04-17 at 21:27 +0800, Zhao, Gang wrote:
>> Dynamic debug function wiphy_dbg() is more convenient for debugging,
>> and if user doesn't enable CONFIG_DYNAMIC_DEBUG, it will fall back to
>> normal static debug, just as what wiphy_debug() does.
>
> Hi.
>
> Your premise is not correct.
>
> wiphy_debug will always emit a message.
>
> wiphy_dbg will only emit a message when #DEBUG
> is #defined or CONFIG_DYNAMIC_DEBUG is enabled
> and the message is specifically enabled by the
> dynamic_debug control file.
>
Yes, you are right. wiphy_debug() will always print a debug level
message. It's not true to wiphy_dbg().
I still prefer to use wiphy_dbg() to print debug messages, since it's
"dynamic", and debug messages may not be needed in normal use.
>> When all the users of wiphy_debug() are gone, wiphy_debug() can be
>> removed.
>
> Not really.
>
Surely wiphy_debug() will be reserved, since wiphy_dbg() can't replace
it.
> Please use git format-patch --cover-letter when
> sending a patch series so that these sorts of
> replies can be done to the cover letter of the
> series instead of individually.
>
> Using a cover-letter "[PATCH 0/N]" also makes it
> easier for maintainers to send acknowledgements
> if applying the entire series.
I will resend the patch set with cover letter(excluding the last
patch). Thanks for your comments.
prev parent reply other threads:[~2014-04-18 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 13:27 [PATCH 1/6] p54: replace wiphy_debug() with wiphy_dbg() Zhao, Gang
2014-04-17 13:27 ` [PATCH 2/6] mac80211_hwsim: " Zhao, Gang
2014-04-17 13:27 ` [PATCH 3/6] adm8211: " Zhao, Gang
2014-04-17 13:27 ` [PATCH 4/6] mwl8k: " Zhao, Gang
2014-04-17 13:27 ` [PATCH 5/6] mac80211: " Zhao, Gang
2014-04-17 13:27 ` [PATCH 6/6] cfg80211: remove function wiphy_debug() Zhao, Gang
2014-04-17 17:15 ` [PATCH 1/6] p54: replace wiphy_debug() with wiphy_dbg() Joe Perches
2014-04-18 7:48 ` Zhao, Gang [this message]
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=87ppkf5b86.fsf@gmail.com \
--to=gamerh2o@gmail.com \
--cc=chunkeey@googlemail.com \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).