Re: [PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event

2006-01-26 Thread Thomas Renninger
Mattia Dongili wrote: On Wed, January 25, 2006 6:23 am, Dmitry Torokhov said: On Wednesday 25 January 2006 00:09, Brown, Len wrote: [...] I have no problem changing the implementation to avoid useless stuff if the patch is going to be considered for acceptance. The other argument against

Re: [PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event

2006-01-25 Thread Mattia Dongili
On Wed, January 25, 2006 2:46 am, Dmitry Torokhov said: On Tuesday 24 January 2006 20:17, Brown, Len wrote: What's the problem with opening a socket to the user-space acpid -- the way multiple readers work today? - one does not want to use current implementation of acpid? - one does not

Re: [PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event

2006-01-25 Thread Mattia Dongili
On Wed, January 25, 2006 6:23 am, Dmitry Torokhov said: On Wednesday 25 January 2006 00:09, Brown, Len wrote: [...] If you remember original code (without registering multiple in-kernel listeners) I think it was more compact that what is in the kernel at the moment. Also IIRC current in kernel

[PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event

2006-01-24 Thread Mattia Dongili
Hello. This patch series revamps an old submission[1] from Dmitry Torokhov that adds support for multiple readers on /proc/acpi/event. Due to the code reorganization happened in the last 1.5 years I re-implemented it a little differently introducing a subscription mechanism to receive events

RE: [PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event

2006-01-24 Thread Brown, Len
What's the problem with opening a socket to the user-space acpid -- the way multiple readers work today? thanks, -Len - To unsubscribe from this list: send the line unsubscribe linux-acpi in the body of a message to [EMAIL PROTECTED] More majordomo info at