From: Lassebq <lassebq.mine@gmail.com>
To: linkinjeon@kernel.org
Cc: amir73il@gmail.com, brauner@kernel.org, cheol.lee@lge.com,
djwong@kernel.org, dsterba@suse.com, ebiggers@kernel.org,
gunho.lee@lge.com, hch@infradead.org, hch@lst.de,
iamjoonsoo.kim@lge.com, jack@suse.cz, jay.sim@lge.com,
josef@toxicpanda.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, neil@brown.name, pali@kernel.org,
rgoldwyn@suse.com, sandeen@sandeen.net, tytso@mit.edu,
viro@zeniv.linux.org.uk, willy@infradead.org, xiang@kernel.org
Subject: Re: [PATCH 00/11] ntfsplus: ntfs filesystem remake
Date: Thu, 23 Oct 2025 00:24:40 +0300 [thread overview]
Message-ID: <45YJ4T.CS9RVQCDTG7F1@gmail.com> (raw)
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.
Ivan
next reply other threads:[~2025-10-22 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 21:24 Lassebq [this message]
[not found] <7YXJ4T.2LNCI9JPXKCZ2@gmail.com>
2025-10-23 7:20 ` [PATCH 00/11] ntfsplus: ntfs filesystem remake Namjae Jeon
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 2:07 Namjae Jeon
2025-10-20 18:33 ` Pali Rohár
2025-10-21 1:49 ` Namjae Jeon
2025-10-21 22:19 ` Pali Rohár
2025-10-22 2:13 ` Namjae Jeon
2025-10-22 18:52 ` Pali Rohár
2025-10-22 22:32 ` Namjae Jeon
2025-10-21 0:17 ` Bagas Sanjaya
2025-10-21 1:55 ` Namjae Jeon
2025-10-26 5:37 ` Bagas Sanjaya
2025-10-22 6:30 ` David Sterba
2025-10-22 8:33 ` Namjae Jeon
2025-10-22 18:57 ` Pali Rohár
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=45YJ4T.CS9RVQCDTG7F1@gmail.com \
--to=lassebq.mine@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=cheol.lee@lge.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=gunho.lee@lge.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=jay.sim@lge.com \
--cc=josef@toxicpanda.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=pali@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiang@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).