From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Daniel Drake <dsd@gentoo.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: STA reassociation improvements
Date: Thu, 19 Jul 2007 14:24:40 -0400 [thread overview]
Message-ID: <20070719182440.GA6603@tuxdriver.com> (raw)
In-Reply-To: <20070717113838.03561c26@logostar.upir.cz>
On Tue, Jul 17, 2007 at 11:38:38AM +0200, Jiri Benc wrote:
> On Mon, 16 Jul 2007 22:15:32 -0400, Daniel Drake wrote:
> > Jiri Benc wrote:
> > > [removed netdev, no reason for sending this there]
> >
> > Was I wrong for sending the patch there, or was it just your ACK that
> > you didn't think would be relevant on netdev?
>
> linux-wireless mailinglist was created to lower traffic at netdev. I
> understand that in the way that wireless patches should be sent to
> linux-wireless only; they will be sent to nedev by John when he's asking
> for a pull. But I'm not sure about that (Cc:ing John), my comment was more
> about my ack.
I think linux-wireless is sufficient, especially for small and/or
isolated patches. But there is no real harm in including netdev,
especially for patches with broader impact. For example, if Zhu Yi
and PJ had chosen to push the multiqueue stuff on wireless first then
it would certainly have been appropriate to copy netdev. I guess
it is just a judgment call -- if your patch merits broader review,
then copy netdev as well.
Hth! (I doubt if it does!)
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2007-07-19 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 14:02 [PATCH v2] mac80211: STA reassociation improvements Daniel Drake
2007-07-16 16:56 ` Jiri Benc
2007-07-17 2:15 ` Daniel Drake
2007-07-17 9:38 ` Jiri Benc
2007-07-19 18:24 ` John W. Linville [this message]
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=20070719182440.GA6603@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dsd@gentoo.org \
--cc=jbenc@suse.cz \
--cc=linux-wireless@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 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.