>>>>> Convert any entry of mutex lock/unlock to guard API and simplify code. >>>> >>>> Thanks that you would like to support another bit of collateral evolution. >>>> >>>> * Would you get into the mood to benefit any more from applications >>>> of scope-based resource management? >>> >>> Why don't you submit them yourself instead of asking others to do work? >> >> 1. The change resistance (or acceptance) is varying for possible software transformations >> in wide ranges, isn't it? > > How would that be any different for anyone else? Maybe not. > Resistance/acceptance should be based on patch quality alone. There are further factors involved also according to usual communication challenges. >> 2. I would appreciate better support and collaboration with additional development resources. > > In what regard? I got the impression that progress would be hindered (or even blocked?) for a while in selected subsystem areas. > What additional resources could you possibly need? Possibly known examples: * More powerful computation equipment? * Software improvements? * Financial incentives? >> 3. I hope that further improvements can be achieved also by the means of >> the semantic patch language (Coccinelle software) in safer and more convenient ways. >> Are you looking for any extensions according to the coccicheck tool? > > Sounds good. Thanks for such positive feedback. > Submit a patch. How long will the integration take (if you would like to take another look at growing product backlogs)? Regards, Markus
