Linux ACPI
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	Marcel Holtmann <marcel@holtmann.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Ian Molton <ian.molton@collabora.co.uk>,
	linux-acpi@vger.kernel.org,
	Corentin Chary <corentincj@iksaif.net>
Subject: Re: rfkill: persistent device suspend/resume
Date: Sat, 28 Nov 2009 11:27:52 -0200	[thread overview]
Message-ID: <20091128132752.GD17373@khazad-dum.debian.net> (raw)
In-Reply-To: <1259413945.5428.21.camel@johannes.local>

On Sat, 28 Nov 2009, Johannes Berg wrote:
> On Sat, 2009-11-28 at 10:41 -0200, Henrique de Moraes Holschuh wrote:
> > What do you guys think?   I will cook up a patch to implement the above, but
> > if there are any objections to the idea, I'd like to hear it ASAP, as I do
> > have a regression to fix :)
> 
> What part of that don't we do?
> 
> static int rfkill_resume(struct device *dev)
> {
>         struct rfkill *rfkill = to_rfkill(dev);
>         bool cur;
> 
>         if (!rfkill->persistent) {
>                 cur = !!(rfkill->state & RFKILL_BLOCK_SW);
>                 rfkill_set_block(rfkill, cur);
>         }

The issue I am reporting is _only_ about persistent devices, so it is the
if(!rfkill->persistent) that is the problem.  It works perfectly for the
other devices.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-11-28 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A37A3E1.8060606@tuffmail.co.uk>
     [not found] ` <1245161645.13461.3.camel@johannes.local>
     [not found]   ` <4A37AEB7.6060405@tuffmail.co.uk>
     [not found]     ` <20090618030806.GE29569@khazad-dum.debian.net>
2009-11-28 12:41       ` rfkill: persistent device suspend/resume Henrique de Moraes Holschuh
2009-11-28 13:12         ` Johannes Berg
2009-11-28 13:27           ` Henrique de Moraes Holschuh [this message]
     [not found]             ` <20091128132752.GD17373-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2009-11-28 13:39               ` Johannes Berg
2009-11-28 17:17                 ` Henrique de Moraes Holschuh
2009-11-28 15:32         ` Alan Jenkins
2009-11-28 16:42           ` Henrique de Moraes Holschuh

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=20091128132752.GD17373@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=corentincj@iksaif.net \
    --cc=ian.molton@collabora.co.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.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