linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rfkill: fix rfkill_set_states() to set the hw state
Date: Mon, 13 Jul 2009 13:30:26 +0200	[thread overview]
Message-ID: <1247484626.4166.5.camel@johannes.local> (raw)
In-Reply-To: <4A5A0941.2000408@tuffmail.co.uk>

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

On Sun, 2009-07-12 at 17:03 +0100, Alan Jenkins wrote:
> The point of this function is to set the software and hardware state at
> the same time.  When I tried to use it, I found it was only setting the
> software state.

Oops, thanks.

Reviewed-by: Johannes Berg <johannes@sipsolutions.net>

This is for 2.6.31, obviously.

> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
> ---
> net/rfkill/core.c |    4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/net/rfkill/core.c b/net/rfkill/core.c
> index 79693fe..db9948e 100644
> --- a/net/rfkill/core.c
> +++ b/net/rfkill/core.c
> @@ -549,6 +549,10 @@ void rfkill_set_states(struct rfkill *rfkill, bool 
> sw, bool hw)
> 	swprev = !!(rfkill->state & RFKILL_BLOCK_SW);
> 	hwprev = !!(rfkill->state & RFKILL_BLOCK_HW);
> 	__rfkill_set_sw_state(rfkill, sw);
> +	if (hw)
> +		rfkill->state |= RFKILL_BLOCK_HW;
> +	else
> +		rfkill->state &= ~RFKILL_BLOCK_HW;
> 
> 	spin_unlock_irqrestore(&rfkill->lock, flags);
> 

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

      reply	other threads:[~2009-07-13 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 16:03 [PATCH] rfkill: fix rfkill_set_states() to set the hw state Alan Jenkins
2009-07-13 11:30 ` Johannes Berg [this message]

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=1247484626.4166.5.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).