Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp872378pxj; Fri, 21 May 2021 00:46:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy4MiAgG5GiQs+i8iMUWKokaM61VFWsEkaPSx+a5hwdNU4KCu7Y7NcXeY/U1Hy/Tg9hlUKq X-Received: by 2002:a05:6402:1115:: with SMTP id u21mr9726069edv.383.1621583167517; Fri, 21 May 2021 00:46:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621583167; cv=none; d=google.com; s=arc-20160816; b=lqpOHxjiz9zJL+RmiE3yQ7Sc+AOYMaermut7qvuh9KnA5j9G6yv1fD44tawX5IO3OG zyNsEj0tJ9NBbi5/DYM/jhYUxkkNDtaQWaj3qo143vBwWnTFD3wODFoVGv/bZ/X0pYZq nXvGuL8tDbAACdc1iBCuqO/Y5P8ZOs3dilPSxQrkQgjjsMWHVhOu1ITuUaWRYfIcKvcg OEZit61caNikPP3zmjKN8kKyCv2o9wt3WGl3q282+lM3755fiIAQ16bZ7Mc23pPvsBgc MpJLGgvKqX/qThO++Uwle1zHuKMNIllDXxFvw6/rT6H18MEOJzAA8LyNcSqP1k3iSNYp XVRg== 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=eVfVXjBnusPfE4BtSdLTYJ0ZoWjGaXNgTiMLq6nMJYM=; b=Rhr+hqFzVHfSEI3CqlTq6Vi2zIt3XLpARH7+OTfcEjO35549gxx+FKzNWoUb/H8fkZ V9UHkTxsl/wDAa3uq/EKPYam4vXz7YOuVpo9Fq+5Foc5YyQhr7+EETEC2/LGaNpTAgVF T9ey/ijkjb5XzLvQ3xW57Tua4kNDS/g7gxECK4SU9aVansqpnrHxZd7HTZUf1F75TGhm lPzf5FosNyQWDMXv5JTcoHdSNahZrZwaRCEd8reWp5ZpTjmkRsNuSuu2Nvh57Gf+oHvN CSyTAOqWojzZbcLu8ZRDZ0cV95DnwFrclf8baA6varyfp3AIyHyL7SxUW6po5bQfiE8M aVdA== 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 n15si5121023edy.288.2021.05.21.00.45.36; Fri, 21 May 2021 00:46:07 -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 S237594AbhETUVZ (ORCPT + 99 others); Thu, 20 May 2021 16:21:25 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:50624 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235930AbhETUVY (ORCPT ); Thu, 20 May 2021 16:21:24 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: shreeya) with ESMTPSA id 8941C1F43E17 Subject: Re: [PATCH v8 4/4] fs: unicode: Add utf8 module and a unicode layer To: Christoph Hellwig Cc: Gabriel Krisman Bertazi , Theodore Ts'o , adilger.kernel@dilger.ca, jaegeuk@kernel.org, chao@kernel.org, ebiggers@google.com, drosen@google.com, ebiggers@kernel.org, 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 References: <20210423205136.1015456-1-shreeya.patel@collabora.com> <20210423205136.1015456-5-shreeya.patel@collabora.com> <20210427062907.GA1564326@infradead.org> <61d85255-d23e-7016-7fb5-7ab0a6b4b39f@collabora.com> <87bl9z937q.fsf@collabora.com> <87mtti6xtf.fsf@collabora.com> <7caab939-2800-0cc2-7b65-345af3fce73d@collabora.com> From: Shreeya Patel Message-ID: <687283ac-77b9-9e9e-dac2-faaf928eb383@collabora.com> Date: Fri, 21 May 2021 01:49:53 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.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 11/05/21 10:05 am, Christoph Hellwig wrote: > On Tue, May 11, 2021 at 02:17:00AM +0530, Shreeya Patel wrote: >> Theodore / Christoph, since we haven't come up with any final decision with >> this discussion, how do you think we should proceed on this? > I think loading it as a firmware-like table is much preferable to > a module with all the static call magic papering over that it really is > just one specific table. Christoph, I get you point here but request_firmware API requires a device pointer and I don't see anywhere it being NULL so I am not sure if we are going in the right way by loading the data as firmware like table.