linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marius Cirsta <mforce2@gmail.com>
To: almaz.alexandrovich@paragon-software.com
Cc: aaptel@suse.com, andy.lavr@gmail.com, anton@tuxera.com,
	dan.carpenter@oracle.com, dsterba@suse.cz, ebiggers@kernel.org,
	hch@lst.de, joe@perches.com, kari.argillander@gmail.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net, mark@harmstone.com,
	nborisov@suse.com, oleksandr@natalenko.name, pali@kernel.org,
	rdunlap@infradead.org, viro@zeniv.linux.org.uk,
	willy@infradead.org
Subject: Re: [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software
Date: Mon, 7 Jun 2021 12:55:59 +0300	[thread overview]
Message-ID: <CANO0Vk5++yd2TmJ9xDPe0-=gpeD5wXpdJpKVVibNVkQW4_czOQ@mail.gmail.com> (raw)

I am just a user of the kernel but for me the ntfs support is really
important as I have shared drives that are in NTFS format and ntfs-3g
is not really the best as it has a high CPU usage.

What happened to this review ? I am not sure what the process is but
is no one really interested ?

I saw there were some comments initially but if those were solved then
is it ready for integration ? Is more testing required? I could help
with that if needed.

             reply	other threads:[~2021-06-07  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  9:55 Marius Cirsta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-28 16:23 [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software Mohammad Rasim
2021-04-02 15:53 Konstantin Komarov
2021-05-19  3:47 ` Neal Gompa
2021-05-19  3:51   ` Neal Gompa
2021-05-20 16:13 ` Darrick J. Wong
2021-07-17 16:36 ` Pali Rohár
2021-07-25 17:02 ` Yan Pas

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='CANO0Vk5++yd2TmJ9xDPe0-=gpeD5wXpdJpKVVibNVkQW4_czOQ@mail.gmail.com' \
    --to=mforce2@gmail.com \
    --cc=aaptel@suse.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=andy.lavr@gmail.com \
    --cc=anton@tuxera.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=ebiggers@kernel.org \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --cc=kari.argillander@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=mark@harmstone.com \
    --cc=nborisov@suse.com \
    --cc=oleksandr@natalenko.name \
    --cc=pali@kernel.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).