Re: [RESEND PATCH 0/1] Use inode_lock/unlock class of provided APIs in filesystems

To: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Subject: Re: [RESEND PATCH 0/1] Use inode_lock/unlock class of provided APIs in filesystems
From: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
Date: Fri, 1 May 2020 12:07:46 +0530
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, willy@xxxxxxxxxxxxx, jlayton@xxxxxxxxxx, ceph-devel@xxxxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, devel@xxxxxxxxxxxxxxxxxx, linux-unionfs@xxxxxxxxxxxxxxx, dsterba@xxxxxxx
In-reply-to: <20200501043741.GK23230@ZenIV.linux.org.uk>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2



On 5/1/20 10:07 AM, Al Viro wrote:

On Wed, Jan 01, 2020 at 04:22:47PM +0530, Ritesh Harjani wrote:

Al, any comments?
Resending this after adding Reviewed-by/Acked-by tags.


.... argh.  My apologies - that got fallen through the cracks.
Could you rebase and resend it?

Np.
Sure, will rebase and resend.

-ritesh

References:
- [RESEND PATCH 0/1] Use inode_lock/unlock class of provided APIs in filesystems
  - From: Ritesh Harjani
- Re: [RESEND PATCH 0/1] Use inode_lock/unlock class of provided APIs in filesystems
  - From: Al Viro