From: Johannes Berg <johannes@sipsolutions.net>
To: Joe Perches <joe@perches.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
libertas-dev@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH wireless-next 00/20] Use pr_<level>
Date: Fri, 15 Jun 2012 09:36:51 +0200 [thread overview]
Message-ID: <1339745811.4512.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <cover.1339739415.git.joe@perches.com> (sfid-20120615_080311_586023_85E50A2D)
On Thu, 2012-06-14 at 22:53 -0700, Joe Perches wrote:
> Update logging style
So ... since we make everybody else explain *why* they make a change, I
think you should too. I don't see a reason for this random patching of
perfectly good code.
johannes
next prev parent reply other threads:[~2012-06-15 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 5:53 [PATCH wireless-next 00/20] Use pr_<level> Joe Perches
2012-06-15 5:53 ` [PATCH wireless-next 05/20] b43: " Joe Perches
2012-06-15 5:53 ` [PATCH wireless-next 06/20] b43legacy: " Joe Perches
2012-06-15 7:36 ` Johannes Berg [this message]
2012-06-15 10:48 ` [PATCH wireless-next 00/20] " Joe Perches
2012-06-15 22:50 ` Ted Ts'o
2012-06-15 23:37 ` 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=1339745811.4512.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=b43-dev@lists.infradead.org \
--cc=joe@perches.com \
--cc=libertas-dev@lists.infradead.org \
--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 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).