From: Joe Perches <joe@perches•com>
To: Kalle Valo <kvalo@codeaurora•org>
Cc: linux-kernel@vger•kernel.org, linux-wireless@vger•kernel.org,
netdev@vger•kernel.org
Subject: Re: [PATCH 0/5] wireless: ti: Convert specialized logging macros to kernel style
Date: Wed, 30 Mar 2016 14:36:31 -0700 [thread overview]
Message-ID: <1459373791.25110.132.camel@perches.com> (raw)
In-Reply-To: <87shz85gkq.fsf@purkki.adurom.net>
On Wed, 2016-03-30 at 14:51 +0300, Kalle Valo wrote:
> Joe Perches <joe@perches•com> writes:
> > Using the normal kernel logging mechanisms makes this code
> > a bit more like other wireless drivers.
> Personally I don't see the point but I don't have any strong opinions. A
> bigger problem is that TI drivers are not really in active development
> and that's I'm not thrilled to take big patches like this for dormant
> drivers.
Not very dormant.
35 patches in the last year, most of them adding functionality.
next prev parent reply other threads:[~2016-03-30 21:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 0:19 [PATCH 0/5] wireless: ti: Convert specialized logging macros to kernel style Joe Perches
2016-03-08 0:19 ` [PATCH 1/5] ti: Convert wl1271_<level> logging macros to dev_<level> or pr_<level> Joe Perches
[not found] ` <760b583e96a9a88f06e97150617f791c3726a302.1457395071.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2016-04-26 9:06 ` Kalle Valo
2016-03-08 0:19 ` [PATCH 2/5] ti: wl1251: Convert wl1251_error to wiphy_err/pr_err Joe Perches
[not found] ` <cover.1457395071.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2016-03-08 0:19 ` [PATCH 3/5] ti: wl1251: Convert wl1251_warning to wiphy_warn Joe Perches
2016-03-08 0:19 ` [PATCH 4/5] ti: wl1251: Convert wl1251_notice to wiphy_info/pr_info Joe Perches
2016-03-08 0:19 ` [PATCH 5/5] ti: wl1251: Convert wl1251_info to wl1251_debug Joe Perches
2016-03-30 11:51 ` [PATCH 0/5] wireless: ti: Convert specialized logging macros to kernel style Kalle Valo
2016-03-30 21:36 ` Joe Perches [this message]
2016-03-31 7:39 ` Kalle Valo
2016-03-31 8:07 ` Joe Perches
2016-03-31 8:59 ` Eliad Peller
2016-04-15 12:22 ` 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=1459373791.25110.132.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=kvalo@codeaurora$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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