[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YMl5Zf1+Q7fop4Qj@infradead.org>
Date: Wed, 16 Jun 2021 05:09:09 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Gabriel Krisman Bertazi <krisman@...labora.com>
Cc: Shreeya Patel <shreeya.patel@...labora.com>,
Christoph Hellwig <hch@...radead.org>,
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 Wed, Jun 02, 2021 at 08:07:07PM -0400, Gabriel Krisman Bertazi wrote:
> I wasn't going to really oppose it from being a firmware but this
> detail, if required, makes the whole firmware idea more awkward. If the
> whole reason to make it a firmware is to avoid the module boilerplate,
> this is just different boilerplate. Once again, I don't know about
> precedent of kernel data as a module, and there is the problem with
> Makefile rules to install this stuff, that I mentioned.
>
> We know we can get rid of the static call stuff already, since we likely
> won't support more encodings anyway, so that would simplify a lot the
> module specific code.
Well, another thing we can do is a data-only module. That is a module
that just contains the tables, with the core code doing a symbol_get
on them.
Powered by blists - more mailing lists