From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Shaohua Li <shaohua.li@intel.com>, Holger Macht <hmacht@suse.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Accardi, Kristen C" <kristen.c.accardi@intel.com>
Subject: Re: [PATCH] bay: Exit if notify handler cannot be installed
Date: Tue, 6 May 2008 12:39:01 -0300 [thread overview]
Message-ID: <20080506153901.GC22828@khazad-dum.debian.net> (raw)
In-Reply-To: <20080506162049.237af49c@core>
On Tue, 06 May 2008, Alan Cox wrote:
> On Tue, 6 May 2008 12:18:46 -0300
> Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> > On Tue, 06 May 2008, Shaohua Li wrote:
> > > The bay driver is duplicated with libata, I thought we should delete it.
> > > See bug http://bugzilla.kernel.org/show_bug.cgi?id=9526
> >
> > The bay driver is currently useless, BUT it should handle a lot of stuff
> > libata won't, such as bay batteries, bay floppies, and anything else in
> > a bay that is not a hard disk.
>
> The bay driver needs to become a service that hands out bay events to
> all the other drivers for that to happen.
Seems sensible. Any pointers? I wouldn't know how to do it (and
actually, right now I am busy working on rfkill for some stuff
thinkpad-acpi needs), but I could try to tack bay after rfkill, if
nobody beats me to it (hint!)
BTW: dock handling might share these issues as well.
The problem has a bit of a hard edge, though: if nobody binds to an ACPI
node that has an EJ0 subnode, bay needs to do it. But if someone wants
to, bay should give the node up, and somehow help that someone handle
the ejection stuff.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-05-06 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 20:25 [PATCH] bay: Exit if notify handler cannot be installed Holger Macht
2008-05-06 9:15 ` Holger Macht
2008-05-06 9:23 ` Shaohua Li
2008-05-06 9:33 ` Holger Macht
2008-05-06 9:35 ` Holger Macht
2008-05-06 15:24 ` Henrique de Moraes Holschuh
2008-05-06 17:12 ` Holger Macht
2008-05-07 1:03 ` Shaohua Li
2008-05-06 15:18 ` Henrique de Moraes Holschuh
2008-05-06 15:20 ` Alan Cox
2008-05-06 15:39 ` Henrique de Moraes Holschuh [this message]
2008-05-06 15:49 ` Alan Cox
2008-05-06 17:17 ` Holger Macht
2008-05-06 17:13 ` Holger Macht
2008-05-07 1:04 ` Shaohua Li
2008-05-07 1:13 ` Henrique de Moraes Holschuh
2008-05-07 1:27 ` Shaohua Li
2008-05-07 12:37 ` Henrique de Moraes Holschuh
2008-05-07 12:43 ` Henrique de Moraes Holschuh
2008-05-07 13:05 ` Holger Macht
2008-05-07 14:17 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 10:45 Holger Macht
2008-05-21 10:59 ` Matthew Garrett
2008-05-21 11:06 ` Holger Macht
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=20080506153901.GC22828@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hmacht@suse.de \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox