[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGudoHGZreXKHGBvkEPOkf=tL69rJD0sTYAV0NJRVS2aA+B5_g@mail.gmail.com>
Date: Mon, 6 Oct 2025 15:16:26 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: Christian Brauner <brauner@...nel.org>
Cc: viro@...iv.linux.org.uk, jack@...e.cz, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, josef@...icpanda.com, kernel-team@...com,
amir73il@...il.com, linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org, ceph-devel@...r.kernel.org,
linux-unionfs@...r.kernel.org
Subject: Re: [PATCH v6 0/4] hide ->i_state behind accessors
On Mon, Oct 6, 2025 at 1:38 PM Christian Brauner <brauner@...nel.org> wrote:
>
> On Mon, Sep 29, 2025 at 02:56:23PM +0200, Mateusz Guzik wrote:
> > This was a stripped down version (no lockdep) in hopes of getting into
> > 6.18. It also happens to come with some renames.
>
> That was not obvious at all and I didn't read that anywhere in the
> commit messages?
>
Well I thought I made it clear in the updated cover letter, we can
chalk it up to miscommunication. Shit happens.
> Anyway, please resend on top of vfs-6.19.inode where I applied your
> other patches! Thank you!
I rebased the patchset on top of vfs-6.19.inode and got a build failure:
fs/ocfs2/super.c:132:27: error: ‘inode_just_drop’ undeclared here (not
in a function)
132 | .drop_inode = inode_just_drop,
| ^~~~~~~~~~~~~~~
and sure enough the commit renaming that helper is missing. Can you
please rebase the branch?
Powered by blists - more mailing lists