From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Joe Perches <joe@perches.com>
Cc: Eugene Krasnikov <k.eugene.e@gmail.com>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>,
wcn36xx <wcn36xx@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
<netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<ath5k-devel@lists.ath5k.org>,
ath9k-devel <ath9k-devel@lists.ath9k.org>,
<ath10k@lists.infradead.org>, <wil6210@qca.qualcomm.com>
Subject: Re: [PATCH] wcn36xx: Fix logging macro with unnecessary semicolon
Date: Fri, 8 Nov 2013 09:06:19 +0200 [thread overview]
Message-ID: <87bo1vcqz8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1383853221.9263.14.camel@joe-AO722> (Joe Perches's message of "Thu, 7 Nov 2013 11:40:21 -0800")
Joe Perches <joe@perches.com> writes:
>> have a
>> second round of convincing ath guys to change printing code. How does
>> that sound?
>
> Luis? Kalle? Other Qualcomm/Atheros folk?
I didn't quite get what you are asking from me. But for me most
important is that the current debugging facilities from user's point of
view don't change. I don't care if the code is in ath10k.ko or ath.ko,
we are talking about ~100 lines of code anyway.
> One of the nominal benefits of separating the ath_<level>
> macros by subsystem was perf/tracing.
Nominal?
--
Kalle Valo
prev parent reply other threads:[~2013-11-08 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 20:40 [PATCH] wcn36xx: Fix logging macro with unnecessary semicolon Joe Perches
2013-11-06 7:49 ` Eugene Krasnikov
2013-11-06 17:55 ` Joe Perches
2013-11-07 7:32 ` Eugene Krasnikov
2013-11-07 19:40 ` Joe Perches
2013-11-08 7:06 ` Kalle Valo [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=87bo1vcqz8.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=joe@perches.com \
--cc=k.eugene.e@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=rodrigue@qca.qualcomm.com \
--cc=wcn36xx@lists.infradead.org \
--cc=wil6210@qca.qualcomm.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).