From: Greg KH <gregkh@suse.de>
To: Norbert Preining <preining@logic.at>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
Johannes Berg <johannes@sipsolutions.net>,
Mattia Dongili <malattia@linux.it>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: sony-laptop: check for rfkill hard block at load time
Date: Fri, 2 Oct 2009 07:38:00 -0700 [thread overview]
Message-ID: <20091002143800.GC21025@suse.de> (raw)
In-Reply-To: <20091002100029.GC4406@gandalf.dynalias.org>
On Fri, Oct 02, 2009 at 07:00:29PM +0900, Norbert Preining wrote:
> On Thu, 24 Sep 2009, Alan Jenkins wrote:
> > We can fix this by querying the firmware at load time and calling
> > rfkill_set_hw_state().
>
> The bug concerning checking the state after suspend to ram should probably
> be also queued. Original email attached.
Queued for what?
confused,
greg k-h
next prev parent reply other threads:[~2009-10-02 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 10:00 sony-laptop: check for rfkill hard block at load time Norbert Preining
2009-10-02 14:38 ` Greg KH [this message]
2009-10-02 15:02 ` Norbert Preining
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=20091002143800.GC21025@suse.de \
--to=gregkh@suse.de \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=malattia@linux.it \
--cc=preining@logic.at \
/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