From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Karol Kozimor
<sziwan-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Alexey Starikovskiy
<alexey.y.starikovskiy-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Matthew Garrett <mjg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/6] ACPI: support system events for .notify
Date: Thu, 30 Apr 2009 09:35:32 -0600 [thread overview]
Message-ID: <20090430153419.12628.91088.stgit@bob.kio> (raw)
This series extends the .notify method I recently added so drivers
can request system notification events as well as device-specific
events. This simplifies some drivers a bit.
Comments welcome.
---
Bjorn Helgaas (6):
ACPI: eeepc-laptop: use .notify method instead of installing handler directly
ACPI: asus-acpi: use .notify method instead of installing handler directly
ACPI: asus-laptop: use .notify method instead of installing handler directly
ACPI: battery: use .notify method instead of installing handler directly
ACPI: ac: use .notify method instead of installing handler directly
ACPI: allow drivers to request both device and system notify events
drivers/acpi/ac.c | 20 +++++---------------
drivers/acpi/battery.c | 22 +++++-----------------
drivers/acpi/bus.c | 6 +++++-
drivers/platform/x86/asus-laptop.c | 23 +++++------------------
drivers/platform/x86/asus_acpi.c | 30 +++++++++++++-----------------
drivers/platform/x86/eeepc-laptop.c | 19 ++++++-------------
include/acpi/acpi_bus.h | 3 +++
7 files changed, 42 insertions(+), 81 deletions(-)
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
next reply other threads:[~2009-04-30 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 15:35 Bjorn Helgaas [this message]
2009-04-30 15:35 ` [PATCH 1/6] ACPI: allow drivers to request both device and system notify events Bjorn Helgaas
2009-05-27 22:41 ` Len Brown
2009-05-28 0:02 ` Bjorn Helgaas
2009-04-30 15:35 ` [PATCH 3/6] ACPI: battery: use .notify method instead of installing handler directly Bjorn Helgaas
[not found] ` <20090430153419.12628.91088.stgit-tBlMHHroXgg@public.gmane.org>
2009-04-30 15:35 ` [PATCH 2/6] ACPI: ac: " Bjorn Helgaas
2009-04-30 15:35 ` [PATCH 4/6] ACPI: asus-laptop: " Bjorn Helgaas
2009-04-30 15:35 ` [PATCH 5/6] ACPI: asus-acpi: " Bjorn Helgaas
2009-04-30 15:36 ` [PATCH 6/6] ACPI: eeepc-laptop: " Bjorn Helgaas
2009-05-27 22:47 ` Len Brown
2009-05-27 22:51 ` [PATCH 0/6] ACPI: support system events for .notify Len Brown
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=20090430153419.12628.91088.stgit@bob.kio \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alexey.y.starikovskiy-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mjg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=sziwan-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox