linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: MR <g7af0ec1e3ea1e7b1@nextmail.ru>
To: "Mohammed Shafi" <shafi.wireless@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	"Rajkumar Manoharan" <rmanohar@qca.qualcomm.com>
Subject: Re: ath9k crash 3.2-rc7
Date: Mon, 09 Jan 2012 11:05:23 +0400	[thread overview]
Message-ID: <NEXT-4f0a91b3e9c7f4.40986810@nextmail.ru> (raw)


 > > Around 23 hours have elapsed.
 > >
 >> WiFi seems to be working 100% of time. It is always at least lightly
 >loaded.
 
45h - all OK.

 > great and thanks a lot for testing!

Doesn't really require _doing_ anything except building patched kernels. And 
it is in my best interest to test the driver for the WiFi card I use...

 > rather than removing the suspicious code
 > this is properly fixed by us with this patch.
 > http://marc.info/?l=linux-wireless&m=132595161516806&w=2

Ah, I saw the message and wondered whether it is the fix I needed and what 
patches should I apply.

So, I am building 3.2 with two patches: over/under-flow catcher (pity that 
it seems to be on a multiple-times-per-second codepath and just leaving the 
checks there for everyone is suboptimal) and allegedely proper fix. Both 
applied OK with a small offset.




             reply	other threads:[~2012-01-09  7:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  7:05 MR [this message]
2012-01-09  7:30 ` ath9k crash 3.2-rc7 Mohammed Shafi
  -- strict thread matches above, loose matches on Subject: below --
2012-01-26 22:19 MR
2012-01-20  4:42 MR
2012-01-20  5:16 ` Mohammed Shafi
2012-01-18 17:30 MR
2012-01-17 18:53 MR
2012-01-18  5:32 ` Mohammed Shafi
2012-01-16 15:52 MR
2012-01-12 18:04 MR
2012-01-11 17:20 MR
2012-01-12  6:06 ` Mohammed Shafi
2012-01-10 18:14 MR
2012-01-11 15:26 ` Mohammed Shafi
2012-01-09 11:11 MR
2012-01-09  7:40 MR
2012-01-09  7:57 ` Mohammed Shafi
2012-01-08  7:19 MR
2012-01-09  5:11 ` Mohammed Shafi
2012-01-07 12:11 MR
2012-01-06 20:55 MR
2012-01-07 11:48 ` Mohammed Shafi
2012-01-06 14:46 MR
2012-01-06 14:50 ` Mohammed Shafi
2012-01-06 12:51 MR
2012-01-06 14:35 ` Mohammed Shafi
2012-01-06 14:41   ` Mohammed Shafi
2012-01-06  8:10 MR
2012-01-06  8:01 MR
2012-01-06  9:02 ` Mohammed Shafi
     [not found] <NEXT-4f069dda9267d2.27061318@nextmail.ru>
     [not found] ` <CAD2nsn3i=HTP6zOEADMx35rOYXDofo7YG+0zCGH36XgZFLfOww@mail.gmail.com>
2012-01-06  7:49   ` Mohammed Shafi
2012-01-05 18:52 MR
2012-01-05 16:32 MR
2012-01-05  6:59 MR
2012-01-05 15:30 ` Mohammed Shafi
2012-01-04 21:18 MR
2012-01-04 21:28 ` John W. Linville
2012-01-05  6:29   ` Mohammed Shafi

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=NEXT-4f0a91b3e9c7f4.40986810@nextmail.ru \
    --to=g7af0ec1e3ea1e7b1@nextmail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmanohar@qca.qualcomm.com \
    --cc=shafi.wireless@gmail.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 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).