From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: eeepc-laptop rfkill, stupid question #4
Date: Mon, 3 Nov 2008 14:55:43 +0000 [thread overview]
Message-ID: <20081103145543.GA496@srcf.ucam.org> (raw)
In-Reply-To: <20081103145145.GD31078@khazad-dum.debian.net>
On Mon, Nov 03, 2008 at 12:51:45PM -0200, Henrique de Moraes Holschuh wrote:
> Not if you can enter or exit HARD_BLOCK, you're not. If you cannot it is
> fine. But if you can, you really need to rfkill_force_state() on resume,
The state can always be overridden by software, so I think we're fine
there.
> And the rfkill core seems to be buggy when you call force_state() on resume,
> which you guys didn't hit because you're not doing it yet. See my other
> email...
Just to make sure: in the case where we *don't* support hard blocking,
there's no need to do anything special in the driver on resume and
rfkill should (but currently doesn't) do the right thing itself?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-11-03 14:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 17:09 eeepc-laptop rfkill, stupid question #4 and 5 Alan Jenkins
2008-10-31 17:11 ` Matthew Garrett
2008-10-31 17:27 ` Alan Jenkins
2008-10-31 20:54 ` Alan Jenkins
2008-11-02 4:00 ` Henrique de Moraes Holschuh
2008-11-02 11:17 ` eeepc-laptop rfkill, stupid question #4 Alan Jenkins
2008-11-02 13:06 ` Matthew Garrett
2008-11-02 13:25 ` Alan Jenkins
2008-11-02 13:26 ` Matthew Garrett
2008-11-03 14:47 ` Henrique de Moraes Holschuh
2008-11-03 14:16 ` Henrique de Moraes Holschuh
2008-11-03 14:18 ` Matthew Garrett
2008-11-03 14:29 ` Alan Jenkins
2008-11-03 14:51 ` Henrique de Moraes Holschuh
2008-11-03 14:55 ` Matthew Garrett [this message]
2008-11-03 15:02 ` Henrique de Moraes Holschuh
2008-11-03 15:08 ` Matthew Garrett
2008-11-03 16:33 ` Henrique de Moraes Holschuh
2008-11-03 18:00 ` rfkill, stupid question #6 Alan Jenkins
2008-11-03 19:06 ` Henrique de Moraes Holschuh
2008-11-04 15:48 ` eeepc-laptop rfkill, stupid question #4 Luiz Fernando N. Capitulino
2008-11-04 15:57 ` Alan Jenkins
2008-11-02 3:46 ` eeepc-laptop rfkill, stupid question #4 and 5 Henrique de Moraes Holschuh
2008-11-02 9:21 ` Matthew Garrett
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=20081103145543.GA496@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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 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.