Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] lib/string: sysfs_streq works case insensitively
To:     Gioh Kim <gi-oh.kim@ionos.com>, linux-kernel@vger.kernel.org,
        akpm@linux-foundation.org
Cc:     ndesaulniers@google.com, gregkh@linuxfoundation.org
References: <20210412113315.91700-1-gi-oh.kim@ionos.com>
From:   Rasmus Villemoes <linux@rasmusvillemoes.dk>
Message-ID: <24530d5a-5611-469e-a4f7-cc704589e9a5@rasmusvillemoes.dk>
Date:   Wed, 28 Apr 2021 08:37:51 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <20210412113315.91700-1-gi-oh.kim@ionos.com>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 12/04/2021 13.33, Gioh Kim wrote:
> As the name shows, it checks the strings inputed from sysfs.
> It should work for both case-sensitive filesystem and
> case-insensitive filesystem. Therefore sysfs_streq should work
> case-insensitively.

What in the whole wide world does case-sensitivity or lack thereof of
filesystems have to do with whether or not the sysfs_streq API should
work case sensitively or not?

The sysfs filesystem itself (1) works like any real UNIX file system
(i.e. case sensitively) and (2) sysfs_streq is not in any way involved
in readdir or lookups or other such filename operations in sysfs.

Very confused,
Rasmus