[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a38a722c0426edf3ca05c6c8143437ffe21aaf7d.camel@kernel.org>
Date: Wed, 22 Jan 2025 15:40:31 -0500
From: Jeff Layton <jlayton@...nel.org>
To: Christoph Hellwig <hch@....de>, Andrew Morton <akpm@...ux-foundation.org>
Cc: Al Viro <viro@...iv.linux.org.uk>, Christian Brauner
<brauner@...nel.org>, Gao Xiang <xiang@...nel.org>, Chao Yu
<chao@...nel.org>, Andreas Gruenbacher <agruenba@...hat.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-erofs@...ts.ozlabs.org, gfs2@...ts.linux.dev
Subject: Re: lockref cleanups
On Wed, 2025-01-15 at 10:46 +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series has a bunch of cosmetic cleanups for the lockref code I came up
> with when reading the code in preparation of adding a new user of it.
>
> Diffstat:
> fs/dcache.c | 3 --
> fs/erofs/zdata.c | 3 --
> fs/gfs2/quota.c | 3 --
> include/linux/lockref.h | 26 ++++++++++++++------
> lib/lockref.c | 60 ++++++++++++------------------------------------
> 5 files changed, 36 insertions(+), 59 deletions(-)
>
Aside from the commit log problem Andreas pointed out in patch #2, this
looks good. Assuming that's fixed:
Reviewed-by: Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists