From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PULL] unicode changes for 7.3
Date: Sat, 22 Aug 2026 17:41:34 -0400 [thread overview]
Message-ID: <87zeydsui9.fsf@mailhost.krisman.be> (raw)
Linus,
This time I have a small fs/unicode pull request for you. Nothing
really fancy, just a clean up and a fix for parsing the unicode version
in the command line. I apologize for not getting it to you during the
first week of the MR, I'm halfway through my summer vacations today.
Please, pull.
The following changes since commit 8ba098e6b6ff0db8edf28528d1552be261af30d4:
Merge tag 'v7.2-rc5-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6 (2026-07-30 17:41:25 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git tags/unicode-for-next-7.3
for you to fetch changes up to a511442085c140da9cdbe60e3f0fab1c71480801:
unicode: Properly reject invalid encoding version strings (2026-07-31 16:33:14 -0400)
----------------------------------------------------------------
This update includes two minor fixes that have been siting on linux-next
for the past weeks.
- A patch from David removing the normalization function that we no
longer use.
- A patch from me fixing a parsing issue in the encoding version
argument passed by filesystems.
----------------------------------------------------------------
Dr. David Alan Gilbert (1):
utf8: Remove unused utf8_normalize
Gabriel Krisman Bertazi (1):
unicode: Properly reject invalid encoding version strings
fs/unicode/utf8-core.c | 30 +++++-------------------------
include/linux/unicode.h | 3 ---
2 files changed, 5 insertions(+), 28 deletions(-)
--
Gabriel Krisman Bertazi
next reply other threads:[~2026-08-22 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 21:41 Gabriel Krisman Bertazi [this message]
2026-08-22 23:58 ` [PULL] unicode changes for 7.3 pr-tracker-bot
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=87zeydsui9.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.