From: "John W. Linville" <linville@tuxdriver.com>
To: javier@cozybit.com
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
johannes@sipsolutions.net, Andrey Yurovsky <andrey@cozybit.com>
Subject: Re: [PATCH v3] Fix regression in mesh forwarding path.
Date: Tue, 7 Jul 2009 13:03:08 -0400 [thread overview]
Message-ID: <20090707170307.GC2768@tuxdriver.com> (raw)
In-Reply-To: <1246935252-19823-1-git-send-email-javier@cozybit.com>
On Mon, Jul 06, 2009 at 07:54:12PM -0700, javier@cozybit.com wrote:
> From: Javier Cardona <javier@cozybit.com>
>
> The removal of the master netdev broke the mesh forwarding path. This patch
> fixes it by using the new internal 'pending' queue.
>
> As a result of this change, mesh forwarding no longer does the inefficient
> 802.11 -> 802.3 -> 802.11 conversion that was done before.
I'm sorry, but this doesn't seem to apply on top of the current tree.
Would you mind taking a look and respinning?
Thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
next prev parent reply other threads:[~2009-07-07 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 0:47 [PATCH] Fix regression in mesh forwarding path javier
2009-07-07 0:52 ` javier
2009-07-07 1:06 ` Johannes Berg
2009-07-07 1:25 ` [PATCH v2] " javier
2009-07-07 1:40 ` Johannes Berg
2009-07-07 3:03 ` Javier Cardona
2009-07-07 2:54 ` [PATCH v3] " javier
2009-07-07 8:50 ` Johannes Berg
2009-07-07 15:30 ` [PATCH v4] " Javier Cardona
2009-07-07 17:03 ` John W. Linville [this message]
2009-07-07 17:55 ` [PATCH v5] " javier
2009-07-10 18:51 ` [PATCH v5] mac80211: " John W. Linville
2009-07-10 19:04 ` Andrey Yurovsky
2009-07-07 1:35 ` [PATCH] " Javier Cardona
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=20090707170307.GC2768@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=andrey@cozybit.com \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=johannes@sipsolutions.net \
--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 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).