All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Basse <michael@alpha-unix.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Stanislaw Gruszka
	<public-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@plane.gmane.org>,
	"John W. Linville"
	<public-linville-2XuSBdqkA4R54TAoqtyWWQ@plane.gmane.org>,
	public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org,
	Ivo van Doorn
	<public-IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>,
	Gertjan van Wingerde
	<public-gwingerde-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>,
	Helmut Schaa
	<public-helmut.schaa-gM/Ye1E23mwN+BqQ9rBEUg@plane.gmane.org>,
	Amir Hedayaty
	<public-hedayaty-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>
Subject: Re: [PATCH] rt2800pci: handle spurious interrupts
Date: Wed, 23 Nov 2011 16:50:57 +0100	[thread overview]
Message-ID: <4ECD1661.2010709@alpha-unix.de> (raw)
In-Reply-To: <20111123073500.GA9833@redhat.com>



Hi

Am 23.11.2011 08:35, schrieb Stanislaw Gruszka:
> Hi
> 
> I do not think my patch fix this problem, but perhaps Gertjan's
> patch do this:
> 
> http://marc.info/?l=linux-wireless&m=132112188308082&w=2
> 
> Note, if you are hitting the same issue, what is fixed by this patch,
> it's enough to do "iwconfig wlan0 power off" to workaround the problem.
> So you can avoid applying the patch, and just use above command and
> check if issue is still reproducible.
> 
> Stanislaw

Thank you very much for that feedback. I have posted that informations
on the ubuntu-bugtracker. I will do some testing with that workaround
and hopefully it is fixing the issue.

Greetings

Michael


  parent reply	other threads:[~2011-11-23 15:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 10:09 [PATCH] rt2800pci: handle spurious interrupts Stanislaw Gruszka
2011-11-16 10:14 ` Ivo Van Doorn
2011-11-16 11:17   ` Stanislaw Gruszka
2011-11-16 11:45     ` Ivo Van Doorn
2011-11-16 10:46 ` Helmut Schaa
2011-11-16 10:52   ` Ivo Van Doorn
2011-11-16 11:01     ` Helmut Schaa
2011-11-22 20:33 ` Michael Basse
2011-11-22 22:10   ` Helmut Schaa
2011-11-23  6:25     ` Michael Basse
     [not found]   ` <20111123073500.GA9833@redhat.com>
2011-11-23 15:50     ` Michael Basse [this message]
2011-11-22 21:49 ` John W. Linville
2011-11-23  8:05   ` Stanislaw Gruszka
2011-11-23  8:50     ` Ivo Van Doorn
2011-11-23  8:51     ` Helmut Schaa
2011-11-23 10:51       ` Stanislaw Gruszka
     [not found]         ` <CAHJ2optb4E2r6W2w21oswptZh=_Q9kB+RbQ=F0TWg9zHGjXwZA@mail.gmail.com>
2011-11-23 14:40           ` Stanislaw Gruszka
2011-11-23 14:45             ` Luis Correia
     [not found]         ` <CAN6fvj2=EhimZUy-DKtpzAKq1mpvBt03KtX9vCi0dBTCXWVsRg@mail.gmail.com>
2011-11-23 15:14           ` Stanislaw Gruszka
2011-11-23 15:44             ` Stanislaw Gruszka
2011-11-23 17:00             ` Stanislaw Gruszka
2011-11-23 20:47         ` David Miller

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=4ECD1661.2010709@alpha-unix.de \
    --to=michael@alpha-unix.de \
    --cc=public-IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
    --cc=public-gwingerde-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
    --cc=public-hedayaty-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
    --cc=public-helmut.schaa-gM/Ye1E23mwN+BqQ9rBEUg@plane.gmane.org \
    --cc=public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org \
    --cc=public-linville-2XuSBdqkA4R54TAoqtyWWQ@plane.gmane.org \
    --cc=public-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@plane.gmane.org \
    --cc=sgruszka@redhat.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.