From: Kalle Valo <kvalo@codeaurora.org>
To: Joe Perches <joe@perches.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-kernel@vger.kernel.org,
Chaoming Li <chaoming_li@realsil.com.cn>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: btcoexist: Convert BTC_PRINTK to btc_<foo>_dbg
Date: Sat, 19 Mar 2016 11:09:50 +0200 [thread overview]
Message-ID: <87pouqhm01.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1458272258.9556.46.camel@perches.com> (Joe Perches's message of "Thu, 17 Mar 2016 20:37:38 -0700")
Joe Perches <joe@perches.com> writes:
> On Thu, 2016-03-17 at 21:54 -0500, Larry Finger wrote:
>> On 03/17/2016 07:00 PM, Joe Perches wrote:
>> > Use a more common logging style.
>
> [ 300K+ quote without comment ]
Yeah, please try to avoid that. For example this makes the patchwork
page for the patch really hard to read:
https://patchwork.kernel.org/patch/8615131/
--
Kalle Valo
next prev parent reply other threads:[~2016-03-19 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 0:00 [PATCH] rtlwifi: btcoexist: Convert BTC_PRINTK to btc_<foo>_dbg Joe Perches
2016-03-18 2:54 ` Larry Finger
2016-03-18 3:37 ` Joe Perches
2016-03-19 9:09 ` Kalle Valo [this message]
2016-04-06 18:39 ` Kalle Valo
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=87pouqhm01.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=joe@perches.com \
--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