Re: [PATCH RFC v4-bis] locking: introduce devm_mutex_init

2023-12-15 Thread Waiman Long
On 12/15/23 10:58, Andy Shevchenko wrote: On Fri, Dec 15, 2023 at 8:23 AM Christophe Leroy wrote: From: George Stark Using of devm API leads to a certain order of releasing resources. So all dependent resources which are not devm-wrapped should be deleted with respect to devm-release order. M

Re: [PATCH RFC v4-bis] locking: introduce devm_mutex_init

2023-12-15 Thread Christophe Leroy
Le 15/12/2023 à 16:58, Andy Shevchenko a écrit : > On Fri, Dec 15, 2023 at 8:23 AM Christophe Leroy > wrote: >> >> From: George Stark >> >> Using of devm API leads to a certain order of releasing resources. >> So all dependent resources which are not devm-wrapped should be deleted >> with respe

Re: [PATCH RFC v4-bis] locking: introduce devm_mutex_init

2023-12-15 Thread Andy Shevchenko
On Fri, Dec 15, 2023 at 8:23 AM Christophe Leroy wrote: > > From: George Stark > > Using of devm API leads to a certain order of releasing resources. > So all dependent resources which are not devm-wrapped should be deleted > with respect to devm-release order. Mutex is one of such objects that >

[PATCH RFC v4-bis] locking: introduce devm_mutex_init

2023-12-14 Thread Christophe Leroy
From: George Stark Using of devm API leads to a certain order of releasing resources. So all dependent resources which are not devm-wrapped should be deleted with respect to devm-release order. Mutex is one of such objects that often is bound to other resources and has no own devm wrapping. Since