Hello Durga, On Tue, Jun 12, 2012 at 8:02 PM, R, Durgadoss <durgadoss.r@xxxxxxxxx> wrote: > Hi Eduardo, > >> >> This patch changes the function thermal_generate_netlink_event >> to receive a thermal zone device instead of a originator id. >> >> This way, the messages will always be bound to a thermal zone. > > I agree with you on this patch implementation. > Ok.. > But I am thinking most user space Apps today are using UEvent based > mechanism, may be it is time for us to re-visit this implemention. > There are standard UEvent parsers available which can be used. > (instead of writing custom netlink parsing implementations) Right... But do we have any legacy application relying on this netlink channel? > > I submitted this patch an year ago, (inspired by some acpi driver, > which uses this same netlink mechanism) and have a couple of > platforms using this. I can change them for my side. Oh.. Ok. Well, on my side, I don't really have any application relying on it. I just want to make sure we don't break things while changing the current implementation. If you are OK to change your applications then fine. We can also, introduce the sysfs notify and mark the netlink as deprecated, while the applications are being modified. Then finally remove it. > > I don't know what other platforms are using this. Need Rui's > help/suggestion here. Indeed. Rui? > > Thanks, > Durga All best, -- Eduardo Valentin _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/linux-pm
