All of lore.kernel.org
 help / color / mirror / Atom feed
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, Eliad Peller <eliad@wizery.com>,
	Guy Mishol <guym@ti.com>,
	Uri Mashiach <uri.mashiach@compulab.co.il>,
	Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 0/5] wireless: ti: Convert specialized logging macros to kernel style
Date: Thu, 31 Mar 2016 01:07:48 -0700	[thread overview]
Message-ID: <1459411668.1744.6.camel@perches.com> (raw)
In-Reply-To: <87y48z3xkz.fsf@purkki.adurom.net>

On Thu, 2016-03-31 at 10:39 +0300, Kalle Valo wrote:
> Joe Perches <joe@perches.com> writes:
> > 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.
> Oh, I didn't realise it had that many patches. But the driver is
> orphaned and doesn't have a maintainer so could I then have an ack from
> one of the active contributors that this ok?

Fine by me.

$ ./scripts/get_maintainer.pl -f --git drivers/net/wireless/ti/

Kalle Valo <kvalo@codeaurora.org> (maintainer:NETWORKING DRIVERS (WIRELESS),commit_signer:27/35=77%)
Eliad Peller <eliad@wizery.com> (commit_signer:9/35=26%,authored:7/35=20%)
Guy Mishol <guym@ti.com> (commit_signer:6/35=17%,authored:5/35=14%)
Johannes Berg <johannes.berg@intel.com> (commit_signer:6/35=17%,authored:3/35=9%)
Uri Mashiach <uri.mashiach@compulab.co.il> (commit_signer:4/35=11%,authored:4/35=11%)

For those people now added to the cc list,
here's the original patch thread:

https://lkml.org/lkml/2016/3/7/1099

  reply	other threads:[~2016-03-31  8:07 UTC|newest]

Thread overview: 16+ 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 ` Joe Perches
2016-03-08  0:19 ` [PATCH 1/5] ti: Convert wl1271_<level> logging macros to dev_<level> or pr_<level> Joe Perches
2016-04-26  9:06   ` Kalle Valo
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
2016-03-08  0:19 ` [PATCH 3/5] ti: wl1251: Convert wl1251_warning to wiphy_warn Joe Perches
2016-03-08  0:19   ` 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
2016-03-31  7:39     ` Kalle Valo
2016-03-31  8:07       ` Joe Perches [this message]
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=1459411668.1744.6.camel@perches.com \
    --to=joe@perches.com \
    --cc=eliad@wizery.com \
    --cc=guym@ti.com \
    --cc=johannes.berg@intel.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=uri.mashiach@compulab.co.il \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.