From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Don Fry <donald.h.fry@intel.com>
Subject: Re: [PATCH wireless-2.6.38] iwlagn: Re-enable RF_KILL interrupt when down
Date: Mon, 7 Feb 2011 11:11:24 +0100 [thread overview]
Message-ID: <20110207101123.GA2319@redhat.com> (raw)
In-Reply-To: <1297013385-9918-1-git-send-email-wey-yi.w.guy@intel.com>
On Sun, Feb 06, 2011 at 09:29:45AM -0800, Wey-Yi Guy wrote:
> From: Don Fry <donald.h.fry@intel.com>
>
> With commit 554d1d027b19265c4aa3f718b3126d2b86e09a08 only one RF_KILL
> interrupt will be seen by the driver when the interface is down.
>
> Re-enable the interrupt when it occurs to see all transitions.
What practical problem this fix? I'm asking, because my RF_KILL commit
went to stable, shouldn't this fix go to stable as well?
Stanislaw
next prev parent reply other threads:[~2011-02-07 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 17:29 [PATCH wireless-2.6.38] iwlagn: Re-enable RF_KILL interrupt when down Wey-Yi Guy
2011-02-07 10:11 ` Stanislaw Gruszka [this message]
2011-02-07 15:35 ` Guy, Wey-Yi W
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=20110207101123.GA2319@redhat.com \
--to=sgruszka@redhat.com \
--cc=donald.h.fry@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wey-yi.w.guy@intel.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).