Harshitha Prem <quic_hprem@xxxxxxxxxxx> writes: >> Like I have said before, for adding any new locks there needs to be >> a >> proper analysis for the locking and good justifications why new locks >> are needed. I don't see any of that above. >> > Sure, Kalle. Will add the details for new locks. As grouping has to be > done in synchronous manner lock was introduced. The problem with Qualcomm code is that new locks seem to be always added without any analysis. But if these new locks are being continuously added the code will become so hard to maintain and convoluted. I can understand adding ath12k_ag_list_lock (it's just badly named) because there is not really any other way to do it. But this mutex_lock looks so suspicious, has anyone analysed that? -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
