From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764875AbYEFPj2 (ORCPT ); Tue, 6 May 2008 11:39:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764920AbYEFPjG (ORCPT ); Tue, 6 May 2008 11:39:06 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:43195 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764888AbYEFPjE (ORCPT ); Tue, 6 May 2008 11:39:04 -0400 X-Sasl-enc: WK+HMbZpdiTbHHOLPwTdZoBLd9x8KonfMshElk9Fg+qK 1210088343 Date: Tue, 6 May 2008 12:39:01 -0300 From: Henrique de Moraes Holschuh To: Alan Cox Cc: Shaohua Li , Holger Macht , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, "Accardi, Kristen C" Subject: Re: [PATCH] bay: Exit if notify handler cannot be installed Message-ID: <20080506153901.GC22828@khazad-dum.debian.net> References: <20080505202508.GA3690@homac> <20080506091522.GA4378@homac> <1210065811.12668.1.camel@sli10-desk.sh.intel.com> <20080506151846.GA22828@khazad-dum.debian.net> <20080506162049.237af49c@core> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080506162049.237af49c@core> X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04 3738 EE25 DE3F 1CDB 0FE3 User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 06 May 2008, Alan Cox wrote: > On Tue, 6 May 2008 12:18:46 -0300 > Henrique de Moraes Holschuh 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