From: Johannes Berg <johannes@sipsolutions.net>
To: Joe Perches <joe@perches.com>
Cc: linux-wireless@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 4/6] mac80211: clean up debugging
Date: Fri, 22 Jun 2012 16:43:23 +0200 [thread overview]
Message-ID: <1340376203.4491.29.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1340375828.31821.11.camel@joe2Laptop> (sfid-20120622_163725_973326_440DEFC6)
On Fri, 2012-06-22 at 07:37 -0700, Joe Perches wrote:
> On Fri, 2012-06-22 at 15:14 +0200, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
> >
> > There are a few things that make the debugging
> > in mac80211 painful:
> > * pr_debug makes it require *both* Kconfig and
> > dynamic configuration -- move to pr_info
>
> pr_info can clutter the log.
Yes, please. We want this information printed unless it's disabled :-)
> > * the macros still need trailing newlines
>
> That's not a bad thing.
People are clearly forgetting them all the time. So I don't see any
reason to not add them in the macros if we're going to have macros
anyway.
> > @@ -317,7 +318,7 @@ ieee80211_agg_splice_packets(struct ieee80211_sub_if_data *sdata,
> > ieee80211_stop_queue_agg(sdata, tid);
> >
> > if (WARN(!tid_tx, "TID %d gone but expected when splicing aggregates"
> > - " from the pending queue\n", tid))
> > + " from the pending queue", tid))
>
>
> defective.
>
> Don't remove newlines in single modules.
Hm, I was under the impression WARN() didn't require a newline. Looks
like either that changed, or I was wrong -- will change this back.
> Using a single style _with_ a newline limits defects and
> limits the likely misuse in other styles.
I'd rather have double newlines once a while than missing ones. I've
seen a lot of bugs with missing newlines, which is rather annoying.
johannes
next prev parent reply other threads:[~2012-06-22 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340370882-9258-1-git-send-email-johannes@sipsolutions.net>
[not found] ` <1340370882-9258-5-git-send-email-johannes@sipsolutions.net>
[not found] ` <1340370882-9258-5-git-send-email-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2012-06-22 14:37 ` [PATCH 4/6] mac80211: clean up debugging Joe Perches
2012-06-22 14:43 ` Johannes Berg [this message]
2012-06-22 14:49 ` Joe Perches
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=1340376203.4491.29.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=joe@perches.com \
--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 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).