linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Felix Fietkau <nbd@openwrt.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	ath9k-devel@lists.ath9k.org, peter@stuge.se,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless-next] MAINTAINERS: Add ATH GENERIC UTILITIES
Date: Wed, 01 Dec 2010 12:16:55 -0800	[thread overview]
Message-ID: <1291234615.1845.196.camel@Joe-Laptop> (raw)
In-Reply-To: <AANLkTinU+jWBXUdW2v9WSL2SZWQn8FHai4+=dAPTASe6@mail.gmail.com>

On Wed, 2010-12-01 at 11:46 -0800, Luis R. Rodriguez wrote:
> On Wed, Dec 1, 2010 at 9:37 AM, Joe Perches <joe@perches.com> wrote:
> > This file pattern is not currently shown as maintained
> > by atheros.  Perhaps it should be?
> > Signed-off-by: Joe Perches <joe@perches.com>
> Sure but its maintained by the community and Atheros hackers, not just me.

No doubt.

$ git log next-20101130 -- drivers/net/wireless/ath/*.[ch] | \
	grep -P "(^Author)" | cut -f2- -d":" | sort | uniq -c | sort -rn | head
     27  Luis R. Rodriguez <lrodriguez@atheros.com>
      6  Felix Fietkau <nbd@openwrt.org>
      4  Bruno Randolf <br1@einfach.org>
      3  Sujith <Sujith.Manoharan@atheros.com>
      3  John W. Linville <linville@tuxdriver.com>
      3  Joe Perches <joe@perches.com>
      3  Bob Copeland <me@bobcopeland.com>
      2  Pavel Roskin <proski@gnu.org>
      2  Johannes Berg <johannes@sipsolutions.net>
      2  David S. Miller <davem@davemloft.net>

Without any sort of MAINTAINERS entry, the results
for files in that directory are like this:

$ ./scripts/get_maintainer.pl -f --rolestats drivers/net/wireless/ath/main.c
"John W. Linville" <linville@tuxdriver.com> (maintainer:NETWORKING [WIREL...)
linux-wireless@vger.kernel.org (open list:NETWORKING [WIREL...)
netdev@vger.kernel.org (open list:NETWORKING DRIVERS)
linux-kernel@vger.kernel.org (open list)

Perhaps you want to be cc'd?
Perhaps there are atheros lists that should be cc'd?
If cc'ing linux-wireless is good enough,
that's good enough for me too.

cheers, Joe


  reply	other threads:[~2010-12-01 20:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 23:53 [PATCH wireless-next] ath: Rename ath_print to ath_debug Joe Perches
2010-11-29  2:17 ` Luis R. Rodriguez
     [not found]   ` <20101129060732.5130.qmail@stuge.se>
2010-11-29 22:41     ` [ath9k-devel] " Felix Fietkau
2010-11-29 22:42       ` Luis R. Rodriguez
2010-11-30  1:39       ` Joe Perches
2010-11-30  2:43         ` Felix Fietkau
2010-11-30 20:19           ` Joe Perches
2010-12-01  7:56             ` Luis R. Rodriguez
2010-12-01  7:59               ` Luis R. Rodriguez
2010-12-01 14:27               ` Joe Perches
2010-12-01 14:37                 ` Felix Fietkau
2010-12-01 17:17                   ` Joe Perches
2010-12-01 17:28                     ` Joe Perches
2010-12-01 17:44                   ` [PATCH] ath: Add and use ath_printk and ath_<level> Joe Perches
2010-12-01 18:05                     ` [PATCH V2] " Joe Perches
2010-12-01 19:08                     ` [PATCH] ath: Convert ath_print(.., ATH_DBG_FATAL to ath_err Joe Perches
2010-12-01 17:37               ` [PATCH wireless-next] MAINTAINERS: Add ATH GENERIC UTILITIES Joe Perches
2010-12-01 19:46                 ` Luis R. Rodriguez
2010-12-01 20:16                   ` Joe Perches [this message]
2010-12-01 20:18                     ` Luis R. Rodriguez
2010-12-01 20:41                       ` [ath9k-devel] " Luis R. Rodriguez
2010-12-02  0:48                         ` 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=1291234615.1845.196.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=nbd@openwrt.org \
    --cc=peter@stuge.se \
    /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).