lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 01 Oct 2019 08:46:44 -0400 From: Qian Cai <cai@....pw> To: Peter Zijlstra <peterz@...radead.org> Cc: akpm@...ux-foundation.org, mingo@...hat.com, will@...nel.org, linux-kernel@...r.kernel.org, linux-api@...r.kernel.org, maarten.lankhorst@...ux.intel.com, mripard@...nel.org, sean@...rly.run, airlied@...ux.ie, daniel@...ll.ch, dri-devel@...ts.freedesktop.org, gregkh@...uxfoundation.org, jslaby@...e.com, viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org, joonas.lahtinen@...ux.intel.com, rodrigo.vivi@...el.com, intel-gfx@...ts.freedesktop.org, tytso@....edu, jack@...e.com, linux-ext4@...r.kernel.org, tj@...nel.org, mark@...heh.com, jlbec@...lplan.org, joseph.qi@...ux.alibaba.com, ocfs2-devel@....oracle.com, davem@...emloft.net, st@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org, bpf@...r.kernel.org, duyuyang@...il.com, juri.lelli@...hat.com, vincent.guittot@...aro.org, hannes@...xchg.org, mhocko@...nel.org, vdavydov.dev@...il.com, cgroups@...r.kernel.org, linux-mm@...ck.org, alexander.levin@...rosoft.com Subject: Re: [PATCH -next] treewide: remove unused argument in lock_release() On Mon, 2019-09-30 at 09:29 +0200, Peter Zijlstra wrote: > On Thu, Sep 19, 2019 at 12:09:40PM -0400, Qian Cai wrote: > > 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. > > Right; I never did this cleanup for not wanting the churn, but as long > as it applies I'll take it. Not sure when you would like to merge this. As you know, the longer it is pending, the more churn it could have. If you could give me rough timeline (i.e., aim for v5.4-rc2 or v5.5), I'll double-check for breakage and rebase it if necessary.
Powered by blists - more mailing lists