[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <687283ac-77b9-9e9e-dac2-faaf928eb383@collabora.com>
Date: Fri, 21 May 2021 01:49:53 +0530
From: Shreeya Patel <shreeya.patel@...labora.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Gabriel Krisman Bertazi <krisman@...labora.com>,
Theodore Ts'o <tytso@....edu>, adilger.kernel@...ger.ca,
jaegeuk@...nel.org, chao@...nel.org, ebiggers@...gle.com,
drosen@...gle.com, ebiggers@...nel.org, yuchao0@...wei.com,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, kernel@...labora.com
Subject: Re: [PATCH v8 4/4] fs: unicode: Add utf8 module and a unicode layer
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.
Powered by blists - more mailing lists