From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
josef@toxicpanda.com, kernel-team@fb.com, amir73il@gmail.com,
linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, ceph-devel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v6 0/4] hide ->i_state behind accessors
Date: Tue, 7 Oct 2025 13:07:51 +0200 [thread overview]
Message-ID: <20251007-warnt-abrutschen-7a6363ce6c54@brauner> (raw)
In-Reply-To: <CAGudoHGZreXKHGBvkEPOkf=tL69rJD0sTYAV0NJRVS2aA+B5_g@mail.gmail.com>
> 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?
Done. Thanks!
prev parent reply other threads:[~2025-10-07 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 10:47 [PATCH v6 0/4] hide ->i_state behind accessors Mateusz Guzik
2025-09-23 10:47 ` [PATCH v6 1/4] fs: provide accessors for ->i_state Mateusz Guzik
2025-09-23 10:47 ` [PATCH v6 2/4] Convert the kernel to use ->i_state accessors Mateusz Guzik
2025-09-23 10:47 ` [PATCH v6 3/4] Manual conversion of ->i_state uses Mateusz Guzik
2025-09-25 10:07 ` Mateusz Guzik
2025-09-29 9:30 ` Christian Brauner
2025-09-23 10:47 ` [PATCH v6 4/4] fs: make plain ->i_state access fail to compile Mateusz Guzik
2025-09-23 11:16 ` [PATCH v6 0/4] hide ->i_state behind accessors Jan Kara
2025-09-23 13:16 ` Dave Chinner
2025-09-29 9:30 ` Christian Brauner
2025-09-29 12:56 ` Mateusz Guzik
2025-10-06 11:38 ` Christian Brauner
2025-10-06 13:16 ` Mateusz Guzik
2025-10-07 11:07 ` Christian Brauner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251007-warnt-abrutschen-7a6363ce6c54@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox