From: Mark Harmstone <mark@harmstone.com>
To: Kari Argillander <kari.argillander@gmail.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: ntfs3@lists.linux.dev
Subject: Re: [PATCH] fs/ntfs3: Fix logic in ntfs_cmp_names_cpu
Date: Mon, 4 Oct 2021 19:25:34 +0100 [thread overview]
Message-ID: <95b14c81-05e8-63ac-5f1e-7dc0c66cdcd5@harmstone.com> (raw)
In-Reply-To: <261705dd-64b2-32e0-e8d6-3be9fa202f0b@harmstone.com>
Kari, Konstantin, what's your conclusion on this? Do you agree that
case-insensitivity is broken at present, or is there something screwy
going on with my set-up?
Mark
next prev parent reply other threads:[~2021-10-04 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 18:33 [PATCH] fs/ntfs3: Fix logic in ntfs_cmp_names_cpu Mark Harmstone
2021-09-28 19:11 ` Kari Argillander
2021-09-28 22:07 ` Kari Argillander
2021-09-28 23:27 ` Mark Harmstone
2021-10-04 18:25 ` Mark Harmstone [this message]
2021-10-06 14:37 ` Konstantin Komarov
2021-10-06 17:03 ` Mark Harmstone
2021-10-07 14:33 ` Konstantin Komarov
2021-10-07 18:26 ` Mark Harmstone
2021-10-07 20:12 ` Kari Argillander
2021-10-07 20:34 ` Mark Harmstone
2021-10-08 5:51 ` Kari Argillander
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=95b14c81-05e8-63ac-5f1e-7dc0c66cdcd5@harmstone.com \
--to=mark@harmstone.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=kari.argillander@gmail.com \
--cc=ntfs3@lists.linux.dev \
/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