[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAKYAXd_CteiFdBsAJ+BMzuRhk1VN=H3k2JdSoSsW0dLMzfXw9A@mail.gmail.com>
Date: Thu, 23 Oct 2025 16:20:34 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: Lassebq <lassebq.mine@...il.com>
Cc: amir73il@...il.com, brauner@...nel.org, cheol.lee@....com,
djwong@...nel.org, dsterba@...e.com, ebiggers@...nel.org, gunho.lee@....com,
hch@...radead.org, hch@....de, iamjoonsoo.kim@....com, jack@...e.cz,
jay.sim@....com, josef@...icpanda.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, neil@...wn.name, pali@...nel.org,
rgoldwyn@...e.com, sandeen@...deen.net, tytso@....edu,
viro@...iv.linux.org.uk, willy@...radead.org, xiang@...nel.org
Subject: Re: [PATCH 00/11] ntfsplus: ntfs filesystem remake
On Thu, Oct 23, 2025 at 6:20 AM Lassebq <lassebq.mine@...il.com> wrote:
>
> Hello
>
> I wanted to apply these patches on top of my kernel build, but I noticed that not every diff is included in the thread. And I think some code in patches appears to be a out of date or target an older kernel? Like there is usage of inode_generic_drop instead of generic_drop_inode.
>
> Is there a reason for that? I'm new to kernel mailing lists so I'm not exactly sure why that's the case or how it works.
>
> Appreciate if you could clear things up for a newbie like me.
ntfsplus patchset is created on the latest kernel(linux-6.18-rc1), and
generic_drop_inode was renamed to inode_generic_drop in
linux-6.18-rc1. So you can apply ntfsplus patchset to 6.18-rc1 or -rc2
and try to build it.
>
> Ivan
Powered by blists - more mailing lists