From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Corey Minyard <minyard@acm.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
yakui.zhao@intel.com, lenb@kernel.org,
linux-acpi@vger.kernel.org,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions
Date: Tue, 27 Jul 2010 14:22:39 +0100 [thread overview]
Message-ID: <20100727132239.GA25190@srcf.ucam.org> (raw)
In-Reply-To: <4C4E340E.3050003@acm.org>
On Mon, Jul 26, 2010 at 08:19:10PM -0500, Corey Minyard wrote:
> I agree that a notifier framework seems like massive overkill for this
> interface. I will note that there are already interfaces for
> registering to receive callbacks when an IPMI device is added or
> removed. What's missing is a way to ask "Is this an ACPI PNP device?".
So we just want something that returns addr_source, along with moving
that enum into a global header?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-07-27 13:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 14:46 [PATCH -v8 0/2] IPMI/ACPI: Install the ACPI IPMI opregion yakui.zhao
2010-07-26 14:46 ` [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions yakui.zhao
2010-07-26 14:46 ` [PATCH_v8 2/2] ACPI: Add the IPMI opregion driver to enable ACPI to access BMC controller yakui.zhao
2010-07-26 16:54 ` Bjorn Helgaas
2010-07-27 0:53 ` ykzhao
2010-07-26 15:11 ` [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions Matthew Garrett
2010-07-26 15:15 ` Matthew Garrett
2010-07-26 16:52 ` Bjorn Helgaas
2010-07-27 0:35 ` ykzhao
2010-07-27 1:19 ` Corey Minyard
2010-07-27 13:22 ` Matthew Garrett [this message]
2010-07-27 14:04 ` Corey Minyard
2010-07-28 1:09 ` ykzhao
2010-07-28 3:30 ` Corey Minyard
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=20100727132239.GA25190@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=yakui.zhao@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).