linux-kernel - Re: [patch 2/3] acpi: Add a docked sysfs file to the dock driver.

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 13 Dec 2006 00:26:38 +0100
From:	Stefan Schmidt <stefan@...enfreihafen.org>
To:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Holger Macht <hmacht@...e.de>, len.brown@...el.com,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Brandon Philips <brandon@...p.org>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: [patch 2/3] acpi: Add a docked sysfs file to the dock driver.

Hello.

On Tue, 2006-12-12 at 15:00, Kristen Carlson Accardi wrote:
> 
> I did have different dock/undock events a few months ago - but
> after some discussion we scrapped them because Kay wants to avoid driver
> specific events.  The "change" event is the only thing that makes sense,
> given the set of uevents available right now, and userspace should be 
> able to handle checking a file to get driver specific details (i.e. dock 
> and undock status).  If you have a specific reason why this won't work,
> let me know.

It's fine with me. I just find two different events more handy.
Checking the file after the event in userspace should not be aproblem.

regards
Stefan Schmidt

Download attachment "signature.asc" of type "application/pgp-signature" (242 bytes)