From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Michael Buesch <mb@bu3sch.de>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
Sujith <Sujith.Manoharan@atheros.com>,
wireless <linux-wireless@vger.kernel.org>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Helmut Schaa <helmut.schaa@googlemail.com>
Subject: Re: ath9k becon loss messages
Date: Tue, 7 Apr 2009 09:53:59 -0400 [thread overview]
Message-ID: <20090407135359.GA28289@tuxdriver.com> (raw)
In-Reply-To: <87fxglhuuc.fsf@litku.valot.fi>
On Tue, Apr 07, 2009 at 08:54:35AM +0300, Kalle Valo wrote:
> "John W. Linville" <linville@tuxdriver.com> writes:
>
> > On Mon, Apr 06, 2009 at 06:18:56PM +0300, Kalle Valo wrote:
> >
> >> When I'm able to implement the proper fix, I think it should first have
> >> proper testing in wireles-testing before pushing it to mainline. So
> >> maybe the proper fix is 2.6.31 material, just to be on the safe side
> >> here.
> >>
> >> John, what do you think?
> >
> > It depends on what the proper fix looks like, but basically anything
> > posted in the last week and thereafter is already 2.6.31 material
> > unless it is a specific bug fix for what is already in Linus' kernel.
>
> Ok, that settles it then. Because this bug has been in mac80211 for ages
> we can wait for 2.6.31.
>
> But do you take Michael's patch[1] for disabling the "beacon loss"
> message for 2.6.30? I think we should have it in 2.6.30, otherwise we
> will get quite a lot of bug reports. Do you want me to resend it?
>
> [1] http://marc.info/?l=linux-kernel&m=123892431619630&w=2
I'll make a note of it.
I took a couple of days off last week and have been poking at other
things, so I'm a bit behind on the merging. If you don't see it in
another week or so then poke me again?
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-04-07 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 9:23 ath9k becon loss messages Jaswinder Singh Rajput
2009-04-05 9:29 ` Michael Buesch
2009-04-05 9:36 ` Michael Buesch
2009-04-05 10:03 ` Kalle Valo
2009-04-05 11:00 ` Jaswinder Singh Rajput
2009-04-05 9:52 ` Jaswinder Singh Rajput
2009-04-05 10:13 ` Kalle Valo
2009-04-06 7:14 ` Helmut Schaa
2009-04-06 8:17 ` Kalle Valo
2009-04-06 8:56 ` Helmut Schaa
2009-04-06 9:04 ` Kalle Valo
2009-04-06 10:17 ` Michael Buesch
2009-04-06 10:23 ` Kalle Valo
2009-04-06 10:51 ` Helmut Schaa
2009-04-06 11:05 ` Kalle Valo
2009-04-06 11:05 ` Kalle Valo
2009-04-06 15:18 ` Kalle Valo
2009-04-06 18:00 ` John W. Linville
2009-04-07 5:54 ` Kalle Valo
2009-04-07 13:53 ` John W. Linville [this message]
2009-04-07 15:19 ` Kalle Valo
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=20090407135359.GA28289@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=davem@davemloft.net \
--cc=helmut.schaa@googlemail.com \
--cc=jaswinder@kernel.org \
--cc=kalle.valo@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.