linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: tomasw@gmail.com, linville@tuxdriver.com, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org, linux-mmc@vger.kernel.org,
	yi.zhu@intel.com, inaky.perez-gonzalez@intel.com,
	cindy.h.kao@intel.com, guy.cohen@intel.com,
	ron.rindjunsky@intel.com, tomas.winkler@intel.com,
	Joe Perches <joe@perches.com>
Subject: Re: [PATCH 1/3] iwmc3200top: Add Intel Wireless MultiCom 3200 top driver.
Date: Sun, 11 Oct 2009 09:40:54 +0200	[thread overview]
Message-ID: <4AD18C06.8040002@gmail.com> (raw)
In-Reply-To: <20091010.185852.133969433.davem@davemloft.net>

David Miller a écrit :
> 
> If it's not in netdev patchwork, I don't plan to add it.
> 
> If it is in patchwork, then it's in my backlog and I'll get to it.
> 
> People should never really have to ask me these questions, that's one
> of the main points of:
> 
> 	http://patchwork.ozlabs.org/project/netdev/list/
> 
> You can always see there what's "pending".


Me wondering if this information could be put in MAINTAINERS or Documentation/ something...

I know it only because I caught one of your answer a while ago :)

Either a per project info, or a global ref to http://patchwork.ozlabs.org/

diff --git a/MAINTAINERS b/MAINTAINERS
index e1da925..18244ad 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3654,6 +3654,7 @@ NETWORKING [GENERAL]
 M:	"David S. Miller" <davem@davemloft.net>
 L:	netdev@vger.kernel.org
 W:	http://www.linuxfoundation.org/en/Net
+W:	http://patchwork.ozlabs.org/project/netdev/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
 S:	Maintained
 F:	net/

  reply	other threads:[~2009-10-11  7:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 23:38 [PATCH 0/3 net] Add iwmc3200top driver Tomas Winkler
2009-09-22 23:38 ` [PATCH 1/3] iwmc3200top: Add Intel Wireless MultiCom 3200 top driver Tomas Winkler
2009-09-22 23:38   ` [PATCH 2/3] iwmc3200wifi: select IWMC3200TOP in Kconfig Tomas Winkler
2009-09-22 23:38     ` [PATCH 3/3] i2400m-sdio: " Tomas Winkler
2009-09-23  0:44       ` Marcel Holtmann
2009-09-23  5:36         ` Tomas Winkler
2009-09-29  9:22     ` [PATCH 2/3] iwmc3200wifi: " Zhu Yi
2009-09-23  6:57   ` [PATCH 1/3] iwmc3200top: Add Intel Wireless MultiCom 3200 top driver Johannes Berg
2009-09-23  7:23     ` Tomas Winkler
2009-09-23  7:34       ` Johannes Berg
2009-09-23 12:29         ` Tomas Winkler
2009-09-23 17:48       ` Inaky Perez-Gonzalez
2009-10-10  9:38   ` Tomas Winkler
2009-10-11  1:58     ` David Miller
2009-10-11  7:40       ` Eric Dumazet [this message]
2009-10-12  6:07         ` David Miller
2009-10-11  8:05       ` Tomas Winkler
2009-10-11 10:36         ` David Miller
2009-10-11 13:07           ` Tomas Winkler
2009-10-12 13:17           ` John W. Linville
2009-10-10 11:01   ` Marcel Holtmann
2009-10-10 18:05     ` Tomas Winkler
2009-10-11  1:59       ` David Miller

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=4AD18C06.8040002@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=cindy.h.kao@intel.com \
    --cc=davem@davemloft.net \
    --cc=guy.cohen@intel.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=joe@perches.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=ron.rindjunsky@intel.com \
    --cc=tomas.winkler@intel.com \
    --cc=tomasw@gmail.com \
    --cc=yi.zhu@intel.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).