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 1/1] MAINTAINERS: mark HPFS as orphaned
Date: Fri, 23 Oct 2026 20:28:07 -0300 [thread overview]
Message-ID: <20261023232807.206097-2-breno3011alves@gmail.com> (raw)
In-Reply-To: <20261023232807.206097-1-breno3011alves@gmail.com>
HPFS has had no active maintenance for a long time. Mikulas Patocka,
who is listed as the maintainer, has confirmed that he uses HPFS only
for personal data shared with OS/2 and is not actively maintaining the
code. The only changes to fs/hpfs/ in recent years are drive-by
cleanups, not functional fixes.
Mark the filesystem as orphaned so that patches are routed to the
linux-fsdevel mailing list, and drop the stale maintainer and website
entries.
The driver remains in the tree. A future removal can be proposed if
no new maintainer or additional users step up.
Signed-off-by: Breno Rodrigues Alves <breno3011alves@gmail.com>
---
MAINTAINERS | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7336600952c8..83685243c8f6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12064,9 +12064,8 @@ F: arch/x86/include/asm/hpet.h
F: arch/x86/kernel/hpet.c
HPFS FILESYSTEM
-M: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
-S: Maintained
-W: http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi
+L: linux-fsdevel@vger.kernel.org
+S: Orphan
F: fs/hpfs/
HS3001 Hardware Temperature and Humidity Sensor
--
2.56.0
prev 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 ` [PATCH v2 0/1] " Breno Rodrigues Alves
2026-10-23 23:28 ` Breno Rodrigues Alves [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=20261023232807.206097-2-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®