Re: Calling device_init_wakeup() on driver removal

2017-01-16 Thread Guenter Roeck
On 01/16/2017 01:50 PM, Rafael J. Wysocki wrote: On Sun, Jan 15, 2017 at 4:23 PM, Guenter Roeck wrote: On 01/15/2017 06:49 AM, Rafael J. Wysocki wrote: On Saturday, January 14, 2017 08:46:05 PM Guenter Roeck wrote: Hi folks, Hi, while looking through driver initialization and removal f

Re: Calling device_init_wakeup() on driver removal

2017-01-16 Thread Rafael J. Wysocki
On Sun, Jan 15, 2017 at 4:23 PM, Guenter Roeck wrote: > On 01/15/2017 06:49 AM, Rafael J. Wysocki wrote: >> >> On Saturday, January 14, 2017 08:46:05 PM Guenter Roeck wrote: >>> >>> Hi folks, >> >> >> Hi, >> >>> while looking through driver initialization and removal functions, I >>> noticed that

Re: Calling device_init_wakeup() on driver removal

2017-01-15 Thread Guenter Roeck
On 01/15/2017 06:49 AM, Rafael J. Wysocki wrote: On Saturday, January 14, 2017 08:46:05 PM Guenter Roeck wrote: Hi folks, Hi, while looking through driver initialization and removal functions, I noticed that many drivers call device_init_wakeup(dev, false) in the removal function. Given tha

Re: Calling device_init_wakeup() on driver removal

2017-01-15 Thread Rafael J. Wysocki
On Saturday, January 14, 2017 08:46:05 PM Guenter Roeck wrote: > Hi folks, Hi, > while looking through driver initialization and removal functions, I noticed > that many drivers > call device_init_wakeup(dev, false) in the removal function. Given that the > driver is about > to be removed, that