Re: [PATCH] video: fbdev: pmag-aa-fb: remove incorrect __exit markups

2017-03-23 Thread Maciej W. Rozycki
On Mon, 20 Mar 2017, Bartlomiej Zolnierkiewicz wrote: > > Even if bus is not hot-pluggable, devices can be unbound from the > > driver via sysfs, so we should not be using __exit annotations on > > remove() methods. The only exception is drivers registered with > > platform_driver_probe() which

Re: [PATCH] video: fbdev: pmag-aa-fb: remove incorrect __exit markups

2017-03-23 Thread Maciej W. Rozycki
On Mon, 20 Mar 2017, Bartlomiej Zolnierkiewicz wrote: > > Even if bus is not hot-pluggable, devices can be unbound from the > > driver via sysfs, so we should not be using __exit annotations on > > remove() methods. The only exception is drivers registered with > > platform_driver_probe() which

Re: [PATCH] video: fbdev: pmag-aa-fb: remove incorrect __exit markups

2017-03-20 Thread Bartlomiej Zolnierkiewicz
On Wednesday, March 01, 2017 03:31:09 PM Dmitry Torokhov wrote: > Even if bus is not hot-pluggable, devices can be unbound from the > driver via sysfs, so we should not be using __exit annotations on > remove() methods. The only exception is drivers registered with > platform_driver_probe() which

Re: [PATCH] video: fbdev: pmag-aa-fb: remove incorrect __exit markups

2017-03-20 Thread Bartlomiej Zolnierkiewicz
On Wednesday, March 01, 2017 03:31:09 PM Dmitry Torokhov wrote: > Even if bus is not hot-pluggable, devices can be unbound from the > driver via sysfs, so we should not be using __exit annotations on > remove() methods. The only exception is drivers registered with > platform_driver_probe() which