From: "John W. Linville" <linville@tuxdriver.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
Matthew Garrett <mjg@redhat.com>,
Andrew Bird <ajb@spheresystems.co.uk>,
Greg Kroah-Hartman <gregkh@suse.de>,
Cezary Jackiewicz <cezary.jackiewicz@gmail.com>,
Philip Langdale <philipl@overt.org>
Subject: Re: [PATCH 5/5] rfkill: remove transmitter blocking on suspend
Date: Tue, 9 Sep 2008 15:22:41 -0400 [thread overview]
Message-ID: <20080909192241.GB3552@tuxdriver.com> (raw)
In-Reply-To: <20080903212020.GA14620@khazad-dum.debian.net>
On Wed, Sep 03, 2008 at 06:20:21PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 03 Sep 2008, John W. Linville wrote:
> > > The following drivers need to check if they need to explicitly block
> > > their transmitters in their own suspend handlers (maintainers Cc'd):
> > > arch/arm/mach-pxa/tosa-bt.c
> > > drivers/net/usb/hso.c
> > > drivers/net/wireless/rt2x00/* (USB might need it?)
> > > drivers/net/wireless/b43/ (SSB over USB might need it?)
> > > drivers/misc/hp-wmi.c
> > > eeepc-laptop w/rfkill support (not in mainline yet)
> > > Compal laptop w/rfkill support (not in mainline yet)
> > > toshiba-acpi w/rfkill support (not in mainline yet)
> >
> > Are we now satisfied that the in-kernel drivers above are all prepared
> > for this patch?
>
> I didn't receive a single response stating that a driver would need special
> care, but then, I didn't receive many responses at all...
OK, I will plan on merging this shortly (let's say on Friday 12
September 2008) unless I hear serious objections.
John
prev parent reply other threads:[~2008-09-09 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 14:57 [GIT PATCH] rfkill changes for 2.6.28, set 1a Henrique de Moraes Holschuh
2008-08-26 14:57 ` [PATCH 1/5] rfkill: use strict_strtoul (v2) Henrique de Moraes Holschuh
2008-08-26 14:57 ` [PATCH 2/5] rfkill: add missing line break Henrique de Moraes Holschuh
2008-08-26 14:57 ` [PATCH 3/5] rfkill: add WARN and BUG_ON paranoia (v2) Henrique de Moraes Holschuh
2008-08-26 15:56 ` Ivo van Doorn
2008-08-26 14:58 ` [PATCH 4/5] rfkill: rename rfkill_mutex to rfkill_global_mutex Henrique de Moraes Holschuh
2008-08-26 14:58 ` [PATCH 5/5] rfkill: remove transmitter blocking on suspend Henrique de Moraes Holschuh
2008-08-26 15:39 ` Greg KH
2008-08-27 4:56 ` Henrique de Moraes Holschuh
2008-08-26 16:13 ` Ivo van Doorn
2008-08-26 19:49 ` Tomas Winkler
2008-08-27 23:01 ` Henrique de Moraes Holschuh
2008-08-28 14:29 ` Ivo van Doorn
2008-08-26 22:56 ` Philip Langdale
2008-09-03 19:05 ` John W. Linville
2008-09-03 21:20 ` Henrique de Moraes Holschuh
2008-09-03 21:31 ` Michael Buesch
2008-09-09 19:22 ` John W. Linville [this message]
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=20080909192241.GB3552@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ajb@spheresystems.co.uk \
--cc=cezary.jackiewicz@gmail.com \
--cc=gregkh@suse.de \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=philipl@overt.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.