From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: eeepc-laptop rfkill, stupid question #4 Date: Mon, 3 Nov 2008 14:18:36 +0000 Message-ID: <20081103141836.GA31894@srcf.ucam.org> References: <490B3BB5.8060801@tuffmail.co.uk> <20081031171126.GA17313@srcf.ucam.org> <490B4014.4040009@tuffmail.co.uk> <490B70A3.8010108@tuffmail.co.uk> <20081102040008.GB29606@khazad-dum.debian.net> <490D8C4E.3010201@tuffmail.co.uk> <20081102130655.GA12766@srcf.ucam.org> <20081103141628.GB31078@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:55349 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755184AbYKCOSo (ORCPT ); Mon, 3 Nov 2008 09:18:44 -0500 Content-Disposition: inline In-Reply-To: <20081103141628.GB31078@khazad-dum.debian.net> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Henrique de Moraes Holschuh Cc: Alan Jenkins , linux-kernel , linux acpi On Mon, Nov 03, 2008 at 12:16:28PM -0200, Henrique de Moraes Holschuh wrote: > Can you read the state? If so, you need to unconditionally do so on resume > (from sleep or hibernation) and rfkill_force_state() it. The rfkill core actually forces the state on resume, so I think we're fine. -- Matthew Garrett | mjg59@srcf.ucam.org