[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120326164910.GF10236@phenom.dumpdata.com>
Date: Mon, 26 Mar 2012 12:49:10 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: "Liu, Jinsong" <jinsong.liu@...el.com>
Cc: "lenb@...nel.org" <lenb@...nel.org>,
"Brown, Len" <len.brown@...el.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"keir.xen@...il.com" <keir.xen@...il.com>,
Jan Beulich <JBeulich@...e.com>,
"Li, Shaohua" <shaohua.li@...el.com>
Subject: Re: [PATCH 2/2] RFC: Xen pad logic
On Mon, Mar 26, 2012 at 07:29:09AM +0000, Liu, Jinsong wrote:
> Konrad Rzeszutek Wilk wrote:
> >> +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?
>
> Not quite clear your point, could you elaborate more?
I was thinking it could do multiple registration of a driver servicing the
same PNPxxx.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists