From: Shreeya Patel <shreeya.patel@collabora.com>
To: krisman@collabora.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Cc: kernel@collabora.com, gustavo.padovan@collabora.com,
andre.almeida@collabora.com,
Shreeya Patel <shreeya.patel@collabora.com>
Subject: [PATCH 0/3] Make UTF-8 encoding loadable
Date: Sun, 14 Mar 2021 04:42:10 +0530 [thread overview]
Message-ID: <20210313231214.383576-1-shreeya.patel@collabora.com> (raw)
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 layer between the filesystems and the utf8 module which will
load the module whenever any filesystem that needs unicode is mounted.
Unicode is the subsystem and utf8 is a charachter encoding for the
subsystem, hence first two patches in the series are renaming functions
and file name to unicode for better understanding the difference between
UTF-8 module and unicode layer.
Last patch in the series adds the layer and utf8 module.
Shreeya Patel (3):
fs: unicode: Rename function names from utf8 to unicode
fs: unicode: Rename utf8-core file to unicode-core
fs: unicode: Add utf8 module and a unicode layer
fs/ext4/hash.c | 2 +-
fs/ext4/namei.c | 12 +-
fs/ext4/super.c | 6 +-
fs/f2fs/dir.c | 12 +-
fs/f2fs/super.c | 6 +-
fs/libfs.c | 6 +-
fs/unicode/Kconfig | 7 +-
fs/unicode/Makefile | 5 +-
fs/unicode/unicode-core.c | 112 +++++++++++++++++
fs/unicode/utf8-core.c | 248 ++++++++++---------------------------
fs/unicode/utf8-selftest.c | 8 +-
fs/unicode/utf8mod.c | 246 ++++++++++++++++++++++++++++++++++++
include/linux/unicode.h | 52 +++++---
13 files changed, 492 insertions(+), 230 deletions(-)
create mode 100644 fs/unicode/unicode-core.c
create mode 100644 fs/unicode/utf8mod.c
--
2.30.1
next reply other threads:[~2021-03-13 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 23:12 Shreeya Patel [this message]
2021-03-13 23:12 ` [PATCH 1/3] fs: unicode: Rename function names from utf8 to unicode Shreeya Patel
2021-03-13 23:12 ` [PATCH 2/3] fs: unicode: Rename utf8-core file to unicode-core Shreeya Patel
2021-03-13 23:12 ` [PATCH 3/3] fs: unicode: Add utf8 module and a unicode layer Shreeya Patel
2021-03-14 1:49 ` Gabriel Krisman Bertazi
2021-03-14 14:46 ` Shreeya Patel
2021-03-15 4:22 ` Gabriel Krisman Bertazi
2021-03-13 23:12 ` [PATCH 3/3] fs: unicode: Make UTF-8 encoding loadable Shreeya Patel
2021-03-14 0:46 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210313231214.383576-1-shreeya.patel@collabora.com \
--to=shreeya.patel@collabora.com \
--cc=andre.almeida@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).