Thread (9 messages) 9 messages, 5 authors, 2019-10-09

Re: [PATCH -next] treewide: remove unused argument in lock_release()

From: Qian Cai <hidden>
Date: 2019-09-20 12:50:43
Also in: bpf, cgroups, dri-devel, intel-gfx, linux-ext4, linux-fsdevel, linux-mm, lkml, netdev

On Fri, 2019-09-20 at 10:38 +0100, Will Deacon wrote:
On Thu, Sep 19, 2019 at 12:09:40PM -0400, Qian Cai wrote:
quoted
Since the commit b4adfe8e05f1 ("locking/lockdep: Remove unused argument
in __lock_release"), @nested is no longer used in lock_release(), so
remove it from all lock_release() calls and friends.

Signed-off-by: Qian Cai <redacted>
---
Although this looks fine to me at a first glance, it might be slightly
easier to manage if you hit {spin,rwlock,seqcount,mutex,rwsem}_release()
first with coccinelle scripts, and then hack lock_release() as a final
patch. That way it's easy to regenerate things if needed.
I am not sure if it worth the extra efforts where I have to retest it on all
architectures, and the patch is really simple, but I can certainly do that if
you insist.

I have just confirmed the patch [1] also applied correctly to the latest
mainline, so it might be the best time just for Linus to merge it directly so it
does not introduce build errors later on?

[1]

https://lore.kernel.org/lkml/1568909380-32199-1-git-send-email-cai@lca.pw/ (local)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help