linux-kernel - Re: patch [0/2]: acpi: add generic removable drive bay support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 8 Sep 2006 16:33:10 -0400
From:	Dave Jones <davej@...hat.com>
To:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	len.brown@...el.com
Subject: Re: patch [0/2]: acpi: add generic removable drive bay support

On Fri, Sep 08, 2006 at 01:21:23PM -0700, Kristen Carlson Accardi wrote:
 > On Fri, 8 Sep 2006 20:58:42 +0100
 > Matthew Garrett <mjg59@...f.ucam.org> wrote:
 > 
 > > On Thu, Sep 07, 2006 at 04:13:05PM -0700, Kristen Carlson Accardi wrote:
 > > 
 > > Firstly, thanks for this - I wrote some related code a while ago. A 
 > > couple of questions...
 > > 
 > > > can then be used by udev to unmount or rescan depending on the event.  It will
 > > > create a proc entry under /proc/acpi/bay for "eject" and for "status".  Writing 
 > > 
 > > Do we really want it under /proc? It would seem to make more sense for 
 > > it to be under /sys.
 > 
 > I agree - this is under proc because this is an acpi driver, and the acpi
 > subsystem is still using the /proc fs for driver/user space interface. I
 > thought I would just conform to their standard.

It's my understanding from talking with Len that he'd like to see /proc/acpi/
go away over time, so adding more to it seems to be at odds with that goal.
 
	Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/