RFC Introduce init() and exit() for platform_device
Get series with b4
b4 am 20090224155721.28880.31830.stgit@ProgramuotojasVersions newest first
- v1 RFC Latest3 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | platform_device: add init() exit() callbacksDocumentation/ drivers/ include/ | +27 | 1 reply | |
| 2/3 | mxc: move serial driver init()/exit() to platform_devicearch/ arch/ arch/ +2 more | +170 | 4 replies | |
| 3/3 | imx-uart: remove unused init()/exit() from platform_dataarch/ arch/ drivers/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] Introduce init() and exit() for platform_device
For changes and documentation about this fix please see:
[RFC PATCH 1/3] platform_device: add init() exit() callbacks
Other patches demonstrate how drivers can benefit from this change.
I have two questions:
1. Is init()/exit() OK? Or should I call it activate()/deactivate()? Other suggestions?
2. Now exit() returns nothing. Maybe it is better if it returned int? How to handle such exit failure?