From: Christian Brauner <brauner@kernel.org>
To: Anton Altaparmakov <anton@tuxera.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
"linux-ntfs-dev@lists.sourceforge.net"
<linux-ntfs-dev@lists.sourceforge.net>,
"ntfs3@lists.linux.dev" <ntfs3@lists.linux.dev>,
Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: [PATCH] Remove NTFS classic
Date: Tue, 16 Jan 2024 12:06:15 +0100 [thread overview]
Message-ID: <20240116-gutgesinnt-autodidaktisch-d1ac1d2f8253@brauner> (raw)
In-Reply-To: <1B634C72-9768-43E9-93B6-3396CBAA958E@tuxera.com>
On Tue, Jan 16, 2024 at 09:51:47AM +0000, Anton Altaparmakov wrote:
> Hi,
>
> It seems there is consensus to remove it so please add:
Well, we'll try. This is one of those cases where we might end up not
being able to do it. But imho this is a case where there's sufficient
reason to at least try and remove this code precisely because we have an
alternative implementation that's been around for a while.
IOW, this isn't like reiserfs where we're actually getting rid of a
filesystem completely.
next prev parent reply other threads:[~2024-01-16 11:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 7:20 [PATCH] fs: Remove NTFS classic Matthew Wilcox (Oracle)
2024-01-15 11:00 ` Anton Altaparmakov
2024-01-15 11:08 ` Enrico Mioso
2024-01-15 11:41 ` Namjae Jeon
2024-01-15 14:49 ` Matthew Wilcox
2024-01-16 9:52 ` [PATCH] " Anton Altaparmakov
2024-01-15 22:20 ` [PATCH] fs: " Dave Chinner
2024-01-16 9:33 ` Christian Brauner
2024-01-16 9:51 ` [PATCH] " Anton Altaparmakov
2024-01-16 11:06 ` Christian Brauner [this message]
2024-01-16 11:32 ` Anton Altaparmakov
2024-03-22 16:35 ` [PATCH] fs: " Johan Hovold
2024-03-25 8:28 ` Christian Brauner
2024-03-25 8:34 ` [PATCH 1/2] ntfs3: serve as alias for the legacy ntfs driver Christian Brauner
2024-03-25 10:09 ` Johan Hovold
2024-03-25 12:01 ` Christian Brauner
2024-03-25 8:34 ` [PATCH 2/2] ntfs3: remove warning Christian Brauner
2024-03-25 10:12 ` Johan Hovold
2024-03-25 12:05 ` Christian Brauner
2024-04-04 8:06 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-11 11:03 ` Konstantin Komarov
2024-04-15 9:54 ` Johan Hovold
2024-04-15 10:20 ` Johan Hovold
2024-04-15 11:32 ` Anton Altaparmakov
2024-04-15 11:42 ` Johan Hovold
2024-04-15 14:15 ` Christian Brauner
2024-04-15 15:23 ` Linus Torvalds
2024-04-15 15:27 ` Matthew Wilcox
2024-04-15 15:47 ` Johan Hovold
2024-04-15 15:51 ` Linus Torvalds
2024-04-15 16:06 ` Johan Hovold
2024-04-16 10:38 ` Christian Brauner
2024-04-16 12:55 ` Johan Hovold
2024-04-17 16:07 ` Konstantin Komarov
2024-04-18 6:36 ` Johan Hovold
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=20240116-gutgesinnt-autodidaktisch-d1ac1d2f8253@brauner \
--to=brauner@kernel.org \
--cc=anton@tuxera.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=ntfs3@lists.linux.dev \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.