From: Breno Rodrigues Alves <breno3011alves@gmail.com>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Breno Rodrigues Alves <breno3011alves@gmail.com>
Subject: [PATCH v2 0/1] MAINTAINERS: mark HPFS as orphaned
Date: Fri, 23 Oct 2026 20:28:06 -0300 [thread overview]
Message-ID: <20261023232807.206097-1-breno3011alves@gmail.com> (raw)
In-Reply-To: <20261023151850.96475-0-breno3011alves@gmail.com>
This is v2 of the HPFS series. Based on the feedback from Mikulas
Patocka on v1, the approach has changed substantially:
- Instead of removing the HPFS driver, mark it as orphaned in
MAINTAINERS and route patches to linux-fsdevel. This respects
Mikulas's use of the filesystem with OS/2 and the fact that
MAINTAINERS still listed him as the maintainer.
- Drop the stale maintainer entry (Mikulas has confirmed he is not
actively maintaining the code) and the personal website URL.
- Keep the driver in the tree. A future removal can be proposed if
no new maintainer or additional users step up.
- The HPFS_SUPER_MAGIC value in include/uapi/linux/magic.h remains
untouched, as does userspace ABI compatibility.
I'm sending this as v2 of the same series rather than as a new thread
so that the discussion stays together. If reviewers prefer a fresh
thread, I'm happy to resend with a new subject.
Breno Rodrigues Alves (1):
MAINTAINERS: mark HPFS as orphaned
MAINTAINERS | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.56.0
next parent reply other threads:[~2026-10-23 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261023151850.96475-0-breno3011alves@gmail.com>
2026-10-23 23:28 ` Breno Rodrigues Alves [this message]
2026-10-23 23:28 ` [PATCH v2 1/1] " Breno Rodrigues Alves
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=20261023232807.206097-1-breno3011alves@gmail.com \
--to=breno3011alves@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--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
all inboxes | Powered by JetHome®