[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <508A89CB020000780008E6ED@nat28.tlf.novell.com>
Date: Fri, 26 Oct 2012 13:02:03 +0100
From: "Jan Beulich" <jbeulich@...e.com>
To: <jinsong.liu@...el.com>
Cc: <xen-devel@...ts.xen.org>, <konrad.wilk@...cle.com>,
<linux-kernel@...r.kernel.org>
Subject: RE: [Xen-devel] [PATCH 1/2] Xen acpi pad implement
>>> "Liu, Jinsong" <jinsong.liu@...el.com> 10/26/12 8:18 AM >>>
>> +static struct acpi_driver xen_acpi_pad_driver = {
>> + .name = "processor_aggregator",
>> + .class = ACPI_PROCESSOR_AGGREGATOR_CLASS,
>> + .ids = pad_device_ids,
>> + .ops = {
>> + .add = xen_acpi_pad_add,
>
>.remove?
>
>[Jinsong] .remove method not used by any logic now (any possible point use it?), so we remove it from our former patch.
Unless there is technical difficulty implementing it, I wouldn't defer adding that code until the point where something doesn't work anymore.
>Overall I'd recommend taking a look at the cleaned up driver in
>our kernels.
>
>[Jinsong] What's your point here?
There's quite a bit of cleanup/simplification potential here, and rather than pointing the pieces out individually I would think comparing with what we have in production use might be worthwhile. But that's up to you of course.
Jan
--
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