Linux filesystem development
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
	"djwong@kernel.org" <djwong@kernel.org>,
	"brauner@kernel.org" <brauner@kernel.org>
Cc: "jack@suse.com" <jack@suse.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"dsterba@suse.cz" <dsterba@suse.cz>,
	"sandeen@redhat.com" <sandeen@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"willy@infradead.org" <willy@infradead.org>,
	"josef@toxicpanda.com" <josef@toxicpanda.com>
Subject: RE: [PATCH] hfs{plus}: add deprecation warning
Date: Thu, 17 Apr 2025 18:10:10 +0000	[thread overview]
Message-ID: <6fcb2ee90de570908eebaf007a4584fc19f1c630.camel@ibm.com> (raw)
In-Reply-To: <0e27414d94d981d4eee45b09caf329fa66084cd3.camel@physik.fu-berlin.de>

Hi Adrian,

On Thu, 2025-04-17 at 11:29 +0200, John Paul Adrian Glaubitz wrote:
> Hello Viacheslav,
> 
> On Wed, 2025-04-16 at 17:56 +0000, Viacheslav Dubeyko wrote:
> > I contributed to HFS+ file system driver more than 10 years ago. And I was
> > completely discouraged because nobody maintained the HFS+ code base. But I would
> > prefer to see the HFS+ in kernel tree instead of complete removal. As far as I
> > can see, we are still receiving some patches for HFS/HFS+ code base. Nowadays, I
> > am mostly busy with CephFS and SSDFS file systems. But if we need more
> > systematic activity on HFS/HFS+, then I can find some time for HFS/HFS+ testing,
> > bug fix, and pathes review. I am not sure that I would have enough time for HFS+
> > active development. But is it really that nobody would like to be the maintainer
> > of HFS/HFS+? Have we asked the contributors and reviewers of HFS/HFS+?
> 
> If you're willing to step up as a maintainer, I would be happy to assist you by
> testing and reviewing patches. I have PowerMacs available for testing and it's
> also possible to just install Debian's 32-bit and 64-bit PowerPC on an emulated
> PowerMac on QEMU using the "mac99" machine types to test booting from an HFS/HFS+
> partition [1].
> 
> I am Debian's primary maintainer of these PowerPC ports in Debian (not to be confused
> with the little-endian PowerPC port) and I can also easily build various test images
> if needed.
> 
> Please let me know if you're interested in working together on the HFS/HFS+ driver.
> 

Sounds good! Yes, I am interested in working together on the HFS/HFS+ driver. :)
And, yes, I can consider to be the maintainer of HFS/HFS+ driver. We can
maintain the HFS/HFS+ driver together because two maintainers are better than
one. Especially, if there is the practical need of having HFS/HFS+ driver in
Linux kernel.

Thanks,
Slava.



  reply	other threads:[~2025-04-17 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  7:51 [PATCH] hfs{plus}: add deprecation warning Christian Brauner
2025-04-15 10:08 ` Jan Kara
2025-04-15 14:49 ` Darrick J. Wong
2025-04-16  6:27   ` Christian Brauner
2025-04-16 15:06     ` Darrick J. Wong
2025-04-16 17:56       ` Viacheslav Dubeyko
2025-04-17  9:29         ` John Paul Adrian Glaubitz
2025-04-17 18:10           ` Viacheslav Dubeyko [this message]
2025-04-17 18:14             ` John Paul Adrian Glaubitz
2025-04-17 21:44               ` Viacheslav Dubeyko
2025-04-23  4:24                 ` Yangtao Li
2025-04-23  4:38                   ` Viacheslav Dubeyko
2025-04-23  6:52                   ` John Paul Adrian Glaubitz
2025-04-17  8:59 ` John Paul Adrian Glaubitz

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=6fcb2ee90de570908eebaf007a4584fc19f1c630.camel@ibm.com \
    --to=slava.dubeyko@ibm.com \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=dsterba@suse.cz \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jack@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox