From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"Brown, Len" <len.brown@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"keir.xen@gmail.com" <keir.xen@gmail.com>,
Jan Beulich <JBeulich@suse.com>,
"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: [PATCH 2/2] RFC: Xen pad logic
Date: Tue, 13 Mar 2012 20:24:42 -0400 [thread overview]
Message-ID: <20120314002442.GC20363@phenom.dumpdata.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350AD0A6@SHSMSX101.ccr.corp.intel.com>
> +static struct acpi_driver xen_acpi_pad_driver = {
> + .name = "processor_aggregator",
> + .class = ACPI_PROCESSOR_AGGREGATOR_CLASS,
> + .ids = xen_pad_device_ids,
> + .ops = {
> + .add = xen_acpi_pad_add,
> + .remove = xen_acpi_pad_remove,
> + },
> +};
> +
> +static int __init xen_acpi_pad_init(void)
> +{
> + return acpi_bus_register_driver(&xen_acpi_pad_driver);
If the acpi_bus_register_driver function could work with multiple
acpi_drivers that define the same class (and have some priority) would
this be easier?
next prev parent reply other threads:[~2012-03-14 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:31 [PATCH 2/2] RFC: Xen pad logic Liu, Jinsong
2012-03-14 0:18 ` Konrad Rzeszutek Wilk
2012-03-26 6:18 ` Liu, Jinsong
2012-03-26 16:38 ` Konrad Rzeszutek Wilk
2012-03-26 16:51 ` Konrad Rzeszutek Wilk
2012-03-14 0:24 ` Konrad Rzeszutek Wilk [this message]
2012-03-26 7:29 ` Liu, Jinsong
2012-03-26 16:49 ` Konrad Rzeszutek Wilk
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=20120314002442.GC20363@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=jinsong.liu@intel.com \
--cc=keir.xen@gmail.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=xen-devel@lists.xensource.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.