| commit | e4a7b9b04de15f6b63da5ccdd373ffa3057a3681 | |
| author | Wolfram Sang <w.sang@pengutronix.de> | |
| Tue, 4 May 2010 09:09:27 +0000 (4 11:09 +0200) | ||
| committer | Jean Delvare <khali@linux-fr.org> | |
| Tue, 4 May 2010 09:09:27 +0000 (4 11:09 +0200) | ||
| tree | 7f2f49df9dc66b334b85f83347df03d2b0d0a721 | treesnapshot (tar.gz zip) |
| parent | d93ac51c7a129db7a1431d859a3ef45a0b1f3fc5 | commitdiff |
i2c-core: Erase pointer to clientdata on removal
After discovering that a lot of i2c-drivers leave the pointer to their
clientdata dangling, it was decided to let the core handle this issue.
It is assumed that the core may access the private data after remove()
as there are no guarantees for the lifetime of such pointers anyhow (see
thread starting at http://lkml.org/lkml/2010/3/21/68)
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
After discovering that a lot of i2c-drivers leave the pointer to their
clientdata dangling, it was decided to let the core handle this issue.
It is assumed that the core may access the private data after remove()
as there are no guarantees for the lifetime of such pointers anyhow (see
thread starting at http://lkml.org/lkml/2010/3/21/68)
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
| Documentation/i2c/writing-clients | diffblobblamehistory | |
| drivers/i2c/i2c-core.c | diffblobblamehistory |