Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Atte Heikkilä" <atteh.mailbox@gmail.com>
To: linkinjeon@kernel.org
Cc: atteh.mailbox@gmail.com, linux-cifs@vger.kernel.org
Subject: Re: [PATCH 1/2] ksmbd: casefold utf-8 share names and fix ascii lowercase conversion
Date: Tue, 13 Sep 2022 20:44:32 +0300	[thread overview]
Message-ID: <20220913174432.22748-1-atteh.mailbox@gmail.com> (raw)
In-Reply-To: <CAKYAXd-pWSWiVy3YMWUpdRGcUS4CNCO8MDDxPin+hQjz4dFPFQ@mail.gmail.com>

On Tue, 13 Sep 2022 23:04:02 +0900, Namjae Jeon wrote:
>2022-09-13 1:14 GMT+09:00, Atte Heikkilä <atteh.mailbox@gmail.com>:
>>
>> This mailing list already has a v2 patch series. Please, reply to that one.
>Okay, but please add cc me when you send the patch to the list.

I sent the v2 patch to the mailing list an hour after the first one:
https://lore.kernel.org/linux-cifs/20220911215542.104935-1-atteh.mailbox@gmail.com/

Please, let's have further discussion as replies to the v2 patch series
and not this one.

>
>> As for your suggestion, I thought to keep the statements separate since the
>> block with the IS_ENABLED() macro is optimized away when CONFIG_UNICODE is
>> not set. I understand that the behavior is the same with your suggestion.
>When CONFIG_UNICODE is not set, um is not checked in my suggestion.

I didn't mean to imply that it was.

>Please tell me why my suggestion is worse. if you are okay, I will
>update it directly.(i.e. no need to send v3 patch).

I didn't mean that your suggestion is worse. Feel free to update it directly
if you'd like.

>and please check the use of strncasecmp() in __caseless_lookup() also.

I thought that the change to utf8_strncasecmp() would be out of place for
this patch series.

>
>And I need to do full test for this patches, I think it will take
>about two days.

Please do not feel inclined to hurry, considering the mistake I managed
to make in the the v1 patch series (this one you're replying to).

>>
>> Thank you.
>>

      reply	other threads:[~2022-09-13 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 20:57 [PATCH 1/2] ksmbd: casefold utf-8 share names and fix ascii lowercase conversion Atte Heikkilä
2022-09-11 20:57 ` [PATCH 2/2] ksmbd-tools: casefold utf-8 share names Atte Heikkilä
2022-09-12 10:20 ` [PATCH 1/2] ksmbd: casefold utf-8 share names and fix ascii lowercase conversion Namjae Jeon
2022-09-12 16:14   ` [PATCH 1/2] ksmbd: casefold utf-8 share names and fix ascii Atte Heikkilä
2022-09-13 14:04     ` Namjae Jeon
2022-09-13 17:44       ` Atte Heikkilä [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=20220913174432.22748-1-atteh.mailbox@gmail.com \
    --to=atteh.mailbox@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.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