Re: MOD_UNLOAD and driver with cdev

2009-01-21 Thread Kostik Belousov
On Wed, Jan 21, 2009 at 05:50:38PM +0200, Andriy Gapon wrote: > on 21/01/2009 17:39 Kostik Belousov said the following: > > On Wed, Jan 21, 2009 at 05:03:20PM +0200, Andriy Gapon wrote: > >> Do I need to code for MOD_UNLOAD for driver module that also creates a > >> cdev? > >> I see in the current

Re: MOD_UNLOAD and driver with cdev

2009-01-21 Thread Andriy Gapon
on 21/01/2009 17:39 Kostik Belousov said the following: > On Wed, Jan 21, 2009 at 05:03:20PM +0200, Andriy Gapon wrote: >> Do I need to code for MOD_UNLOAD for driver module that also creates a cdev? >> I see in the current code that one strategy is to simply call >> destroy_dev(). I guess detach r

Re: MOD_UNLOAD and driver with cdev

2009-01-21 Thread Kostik Belousov
On Wed, Jan 21, 2009 at 05:03:20PM +0200, Andriy Gapon wrote: > > Do I need to code for MOD_UNLOAD for driver module that also creates a cdev? > I see in the current code that one strategy is to simply call > destroy_dev(). I guess detach routines are called automatically and > destroy_dev can be

MOD_UNLOAD and driver with cdev

2009-01-21 Thread Andriy Gapon
Do I need to code for MOD_UNLOAD for driver module that also creates a cdev? I see in the current code that one strategy is to simply call destroy_dev(). I guess detach routines are called automatically and destroy_dev can be done there as well.. Is it reasonable to refuse unload if cdev is in us