public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Frans Pop <elendil@planet.nl>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
	linux-wireless@vger.kernel.org, Netdev <netdev@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Subject: Re: [2.6.31-rc1] iwlagn (4965): no wireless due to RFKILL problem
Date: Fri, 26 Jun 2009 22:28:52 +0200	[thread overview]
Message-ID: <1246048132.21314.75.camel@johannes.local> (raw)
In-Reply-To: <200906261410.58808.elendil@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

On Fri, 2009-06-26 at 14:10 +0200, Frans Pop wrote:

> Well, with 2.6.30 hp-wmi worked together with rfkill without problems.
> Looking at the commit logs, it looks like the rfkill rewrite by Johannes 
> and Alan is the cause here. CCs added.

Hmm, looks like there might be another polarity error, try this:
-       int query = BIT(b + 8) | ((!!blocked) << b);
+       int query = BIT(b + 8) | ((!blocked) << b);


johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-06-27  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 11:36 [2.6.31-rc1] iwlagn (4965): no wireless due to RFKILL problem Frans Pop
     [not found] ` <200906261336.29318.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2009-06-26 11:59   ` Maciej Rutecki
     [not found]     ` <8db1092f0906260459n308311faweb6d9733cdd1eb13-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-26 12:10       ` Frans Pop
2009-06-26 20:28         ` Johannes Berg [this message]
2009-06-27  9:49           ` Maciej Rutecki
2009-06-27  9:49           ` Frans Pop

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=1246048132.21314.75.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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