Hi Jean, do you have already something in mind how to proceed with the i2c_setclientdata-topic? I could offer the following: I modify my semantic patch to remove all set_clientdata(NULL) calls connected to a kfree(). Then, we could have a look if there are still some left and investigate why. Once all issues are resolved (maybe there are none), we should know what to add in the core-layer, hopefully just the call to set_clientdata. Regarding this comment: > the core should just set the client data to NULL. If there are drivers that > rely on the current behavior, then those drivers should be reviewed first as > to the reason why they need it. I could check if there is any probe-function calling get_clientdata and making use of that? That is probably the most obvious thing which would need to rely on the current behaviour or did I miss something? Have a nice weekend, Wolfram -- Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ |
Attachment:
signature.asc
Description: Digital signature