Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4237718pxf; Tue, 30 Mar 2021 02:51:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyE0jm614uLS35S6xQhokpah1gqROsMq1xkPCaWyBJ+p45Df9T560FpSNzY37rDqjbDq5I8 X-Received: by 2002:a17:907:216a:: with SMTP id rl10mr32838410ejb.365.1617097888798; Tue, 30 Mar 2021 02:51:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617097888; cv=none; d=google.com; s=arc-20160816; b=beT6G36aeG/olV0SVnP2Y3VRQSKVuZkK+atMOK4So6pqyKCSzD8BlehE43DhsLMuto b2k9NQtwdDg3tY72QuZTW51//hx+ew6zKsRS7CmOc7QEIEsMmt8l2R1ESM/0/Iadg59q 5//rDAMTv3b1+6cbNwcFiQvwa1SX3BE5XRtY7cwgEycJ0CE+PBtkbePo928uSu553a6M LR96pKxSLGIknVRyXcUiH40pzpwZo9V8j42xViFMfUDWb4zDJpOrJyS3hi7IOeni6wGc OdSk5ZggmCesNk0B36h8hqQL3o+pwoZJQv5PBCHITd7itzKl7PFK/MnSzOMhi+Rq+H7q OgsA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=fol2B8uhriAUFfDP+lph+V3Oi96wdqD5ohfbwLf40fA=; b=YdcbuOEt3UtSm3fqo0OA+qjwStlS83301Kwb2lH3TaoFDnF6Mob36s8kucD54N40Zi jJDhyo5TSOjbAU+hEGFTih8A7i8TMUnMcZ5n15+Bn3x4Ez2Lg10tZ36q2deMM6uRHnAw NtHjqXSbhYNTeFIUWRgWBaKH7thTr0v2ZMicRtbi9U/oHZxBIW2y+X56fi3i6kAb/Qlo 3WFxO1PNKnTDP1aFcungZiE3CUX3V4y45WrtC2/4rSUQ7aznhrwDkOXNaq2mJ9LD2x5j IAD0CSltdGunFSMIGI0ZhPayfqy41OqXPnklu9lXB7LhCjjNZviudsNjWbBHCTr0G8h6 DCGw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ji4si15884482ejc.235.2021.03.30.02.50.56; Tue, 30 Mar 2021 02:51:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231567AbhC3JuM (ORCPT + 99 others); Tue, 30 Mar 2021 05:50:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41168 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231549AbhC3Jts (ORCPT ); Tue, 30 Mar 2021 05:49:48 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A0CCCC061574; Tue, 30 Mar 2021 02:49:48 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: shreeya) with ESMTPSA id B13D91F452F3 Subject: Re: [PATCH v5 2/4] fs: unicode: Rename function names from utf8 to unicode To: Eric Biggers Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jaegeuk@kernel.org, chao@kernel.org, krisman@collabora.com, drosen@google.com, yuchao0@huawei.com, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, kernel@collabora.com, andre.almeida@collabora.com References: <20210329204240.359184-1-shreeya.patel@collabora.com> <20210329204240.359184-3-shreeya.patel@collabora.com> From: Shreeya Patel Message-ID: Date: Tue, 30 Mar 2021 15:19:37 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On 30/03/21 7:23 am, Eric Biggers wrote: > On Tue, Mar 30, 2021 at 02:12:38AM +0530, Shreeya Patel wrote: >> utf8data.h_shipped has a large database table which is an auto-generated >> decodification trie for the unicode normalization functions and it is not >> necessary to carry this large table in the kernel. >> Goal is to make UTF-8 encoding loadable by converting it into a module >> and adding a unicode subsystem layer between the filesystems and the >> utf8 module. >> This layer will load the module whenever any filesystem that >> needs unicode is mounted. >> utf8-core will be converted into this layer file in the future patches, >> hence rename the function names from utf8 to unicode which will denote the >> functions as the unicode subsystem layer functions and this will also be >> the first step towards the transformation of utf8-core file into the >> unicode subsystem layer file. >> >> Signed-off-by: Shreeya Patel >> --- >> Changes in v5 >> - Improve the commit message. > This didn't really answer my questions about the reason for this renaming. > Aren't the functions like unicode_casefold() still tied to UTF-8 (as opposed to > e.g. supporting both UTF-8 and UTF-16)? Is that something you're trying to > change? Currently, layer's functions are still tied to UTF-8 encoding only. But in future if we will have UTF-16 support then layer file would have to be changed accordingly to support both. Unicode subsystem layer is a generic layer which connects the filesystems and UTF8 module ( and/or UTF16 in future ) > > - Eric >