From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
willy@linux.intel.com, lrodriguez@atheros.com
Subject: Re: ath5k gets lost with eeepc-laptop removal
Date: Fri, 31 Oct 2008 14:23:18 +0000 [thread overview]
Message-ID: <20081031142318.GA9009@srcf.ucam.org> (raw)
In-Reply-To: <490B0D75.8020601@tuffmail.co.uk>
On Fri, Oct 31, 2008 at 01:51:49PM +0000, Alan Jenkins wrote:
> Matthew: I nagged you twice about different consequences of this
> commit, so here's a third :). You said rfkill no longer automatically
> frobs on suspend/resume, which was what I was worried about last time.
> Should the core code also be modified so it doesn't do anything when
> the rfkill device is unregistered?
I think there's definitely an argument in favour of that, though I
suspect that's a design feature - if you remove the control mechanism
for a radio, the safe state for that radio to be in is not transmitting.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-10-31 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 13:05 ath5k gets lost with eeepc-laptop removal Luiz Fernando N. Capitulino
2008-10-31 13:51 ` Alan Jenkins
2008-10-31 14:23 ` Matthew Garrett [this message]
2008-10-31 18:35 ` Nick Kossifidis
2008-11-02 9:23 ` Matthew Garrett
2008-10-31 16:26 ` Nick Kossifidis
2008-10-31 17:19 ` Luiz Fernando N. Capitulino
2008-10-31 18:33 ` Nick Kossifidis
2008-10-31 18:43 ` Luiz Fernando N. Capitulino
2008-10-31 18:48 ` Luiz Fernando N. Capitulino
2008-11-02 9:04 ` 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=20081031142318.GA9009@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=willy@linux.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 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.