[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240903113658.GA1002375@mit.edu>
Date: Tue, 3 Sep 2024 07:36:58 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: André Almeida <andrealmeid@...lia.com>
Cc: Hugh Dickins <hughd@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
krisman@...nel.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, kernel-dev@...lia.com,
Daniel Rosenberg <drosen@...gle.com>, smcv@...labora.com,
Christoph Hellwig <hch@....de>,
Gabriel Krisman Bertazi <gabriel@...sman.be>
Subject: Re: [PATCH v2 2/8] unicode: Create utf8_check_strict_name
I'd suggest using the one-line summary:
unicode: create the helper function utf8_check_strict_name()
so that it's a bit more descriptive.
On Mon, Sep 02, 2024 at 07:55:04PM -0300, André Almeida wrote:
> +/**
> + * utf8_check_strict_name - Check if a given name is suitable for a directory
> + *
> + * This functions checks if the proposed filename is suitable for the parent
> + * directory. That means that only valid UTF-8 filenames will be accepted for
> + * casefold directories from filesystems created with the strict enconding flags.
> + * That also means that any name will be accepted for directories that doesn't
> + * have casefold enabled, or aren't being strict with the enconding.
I also suggest wrapping with a fill column of 72 characters, instead
of 80.
- Ted
Powered by blists - more mailing lists