From: Thomas Renninger <acpi@renninger.de>
To: Mattia Dongili <malattia@linux.it>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
"Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, Robert Love <rml@novell.com>,
kasievers@suse.de
Subject: Re: [PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event
Date: Thu, 26 Jan 2006 18:38:20 +0100 [thread overview]
Message-ID: <43D9090C.1030306@renninger.de> (raw)
In-Reply-To: <10537.83.103.117.254.1138182891.squirrel@picard.linux.it>
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 is why enhance an interface when
>>> perhaps we should instead consider replacing it altogether...
>
> The same thing has been said at Dmitry's submission (08/2004) and
> /proc/acpi/event is still there. :)
> Also, removing /proc/acpi/event will take a very long time.
> Anyway what would you suggest (if you have already some plan)? I'd like to
> try implementing it.
What about the dbus-kernel interface?
Acpi events are probably one of the things that should
make use of this one sooner or later?
However I have no idea in which state dbus is on kernel side.
Thomas
next prev parent reply other threads:[~2006-01-26 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 5:09 [PATCH 0/2] Deliver ACPI events upon subscription and implement multiple readers for /proc/acpi/event Brown, Len
2006-01-25 5:23 ` Dmitry Torokhov
2006-01-25 9:54 ` Mattia Dongili
2006-01-26 17:38 ` Thomas Renninger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-25 1:17 Brown, Len
2006-01-25 1:46 ` Dmitry Torokhov
2006-01-25 8:16 ` Mattia Dongili
2006-01-24 23:14 Mattia Dongili
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=43D9090C.1030306@renninger.de \
--to=acpi@renninger.de \
--cc=dtor_core@ameritech.net \
--cc=kasievers@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=malattia@linux.it \
--cc=rml@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.