mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/3] ACPI / dock: Rework the handling of dock notifications
Date: Tue, 11 Feb 2014 01:09:32 +0100	[thread overview]
Message-ID: <3728252.WpMGKRKmqq@vostro.rjw.lan> (raw)

Hi All,

This is on top of the current linux-next branch of linux-pm.git.

The handling of ACPI dock notifications doesn't require a notify handler to
be installed for every dock device object.  Moreover, the namespace doesn't
have to be scanned upfront to discover those objects and the ACPI container
code should be made avoid trying to handle dock notifications (in case dock
stations have container device IDs).

The series makes the changes following from the above observations and a
couple of improvements on top of them.

[1/3] Dispatch ACPI dock notifications from the global notify handler.
[2/3] Pass ACPI device pointer to acpi_device_is_battery() (which is a new
      helper function added by [1/3]).
[3/3] Associate dock platform devices with ACPI device objects

Thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

             reply	other threads:[~2014-02-10 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  0:09 Rafael J. Wysocki [this message]
2014-02-11  0:10 ` [PATCH 1/3] ACPI / dock: Dispatch dock notifications from the global notify handler Rafael J. Wysocki
2014-02-14  0:45   ` [Update][PATCH " Rafael J. Wysocki
2014-02-11  0:10 ` [PATCH 2/3] ACPI / dock: Pass ACPI device pointer to acpi_device_is_battery() Rafael J. Wysocki
2014-02-11  0:11 ` [PATCH 3/3] ACPI / dock: Associate dock platform devices with ACPI device objects Rafael J. Wysocki

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=3728252.WpMGKRKmqq@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®