All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Javier Cardona <javier@cozybit.com>
Cc: Steve Derosier <steve@cozybit.com>,
	devel@lists.open80211s.org, linux-wireless@vger.kernel.org,
	Jiri Slaby <jirislaby@gmail.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Bob Copeland <me@bobcopeland.com>
Subject: Re: ath5k: Fixes for mesh operation
Date: Tue, 7 Dec 2010 15:57:14 -0500	[thread overview]
Message-ID: <20101207205713.GI2700@tuxdriver.com> (raw)
In-Reply-To: <AANLkTik5bGXyWsz0CeVemZ-s9uWC+SOyJNzfxr1vcoGt@mail.gmail.com>

Waiting on davem to process my last pull request...

On Tue, Dec 07, 2010 at 11:12:55AM -0800, Javier Cardona wrote:
> John,
> 
> Are you waiting for acks from ath5k maintainers to apply this series?
> 
> https://patchwork.kernel.org/patch/369461/
> https://patchwork.kernel.org/patch/369471/
> https://patchwork.kernel.org/patch/369481/
> 
> Thanks!
> 
> Javier
> 
> On Tue, Nov 30, 2010 at 6:18 PM, Javier Cardona <javier@cozybit.com> wrote:
> > After applying these fixes we were able to successfully bring up mesh
> > interfaces and establish peer links with ath9k devices.
> >
> > One issue still looms with both athX drivers:  you have to issue a scan to get
> > mesh beaconing started.  Keep that in mind if you try and test these fixes.
> >
> >
> 
> 
> 
> -- 
> Javier Cardona
> cozybit Inc.
> http://www.cozybit.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2010-12-07 21:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  2:18 ath5k: Fixes for mesh operation Javier Cardona
2010-12-01  2:18 ` [PATCH 1/3] ath5k: Fix beaconing in mesh mode Javier Cardona
2010-12-01 13:16   ` Bob Copeland
2010-12-01 18:23     ` Javier Cardona
2010-12-02  1:16       ` Bruno Randolf
2010-12-07 20:58   ` John W. Linville
2010-12-07 21:35     ` Javier Cardona
2010-12-01  2:18 ` [PATCH 2/3] ath5k: Prevent mesh interfaces from being counted as ad-hoc Javier Cardona
2010-12-07 20:58   ` John W. Linville
2010-12-07 21:36     ` Javier Cardona
2010-12-01  2:18 ` [PATCH 3/3] ath5k: Put the right tsf value in mesh beacons Javier Cardona
2010-12-07 20:57   ` John W. Linville
2010-12-07 21:37     ` Javier Cardona
2010-12-07 19:12 ` ath5k: Fixes for mesh operation Javier Cardona
2010-12-07 20:57   ` 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=20101207205713.GI2700@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=devel@lists.open80211s.org \
    --cc=javier@cozybit.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=steve@cozybit.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 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.