All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: Peter Chubb <peter.chubb@nicta.com.au>
Cc: me@bobcopeland.com, linux-wireless@vger.kernel.org
Subject: Re: Commit 6b5d,.. breaks ath5k in WPA-enabled networks
Date: Mon, 31 May 2010 19:26:34 +0900	[thread overview]
Message-ID: <201005311926.34371.br1@einfach.org> (raw)
In-Reply-To: <w47hmkh1b4.wl%peter@chubb.wattle.id.au>

On Monday 31 May 2010 18:23:43 Peter Chubb wrote:
> With Linus's current head-of-tree my ath5k cannot associate with
> WPA-enabled access points.  I bisected back to this patch:
> 
> 	    Since commit 6b5d117eddc09cd976ad8030d715f4350f598a22
> 	    ath5k: clean up queue manipulation
> 
> I suspect at least one of the two wake-up calls that were removed is
> actually necessary.
> 
> Reverting the patch restores correct behaviour.

try this, please:

https://patchwork.kernel.org/patch/100681/

i have sent the patch a long time ago but it didnt get merged yet.

bruno

> --
> Dr Peter Chubb                                  peter DOT chubb AT
> nicta.com.au http://www.ertos.nicta.com.au               ERTOS within
> National ICT Australia All things shall perish from under the sky/Music
> alone shall live, never to die --
> 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

  reply	other threads:[~2010-05-31 10:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31  9:23 Commit 6b5d,.. breaks ath5k in WPA-enabled networks Peter Chubb
2010-05-31 10:26 ` Bruno Randolf [this message]
2010-05-31 11:25   ` Peter Chubb
2010-05-31 12:56     ` me
2010-06-01  3:55       ` Bruno Randolf
2010-06-01  4:03         ` Peter Chubb
2010-05-31 20:05 ` Jaroslav Fojtik

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=201005311926.34371.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=peter.chubb@nicta.com.au \
    /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.