Re: [RFC PATCH 0/7] Add managed version of delayed work init

2021-02-19 Thread Matti Vaittinen
Hello Mark, Thanks for taking a look at the series! This is the first time anyone has been commenting on a cover-letter which is likely to fade away and never be looked at again. Guess you are a thorough person :) On Thu, 2021-02-18 at 08:28 -0800, mark gross wrote: > On Sat, Feb 13, 2021 at 01:5

Re: [RFC PATCH 0/7] Add managed version of delayed work init

2021-02-18 Thread mark gross
On Sat, Feb 13, 2021 at 01:58:17PM +0200, Matti Vaittinen wrote: > It's not rare that device drivers need delayed work. > It's not rare that this work needs driver's data. > > Often this means that driver must ensure the work is not queued when > driver exits. Usually this is done by ensuring new

[RFC PATCH 0/7] Add managed version of delayed work init

2021-02-13 Thread Matti Vaittinen
It's not rare that device drivers need delayed work. It's not rare that this work needs driver's data. Often this means that driver must ensure the work is not queued when driver exits. Usually this is done by ensuring new work is not added and then calling cancel_delayed_work_sync() at remove().