linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: tytso@mit.edu
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fs/unicode: Changes for v5.4-rc1
Date: Tue, 17 Sep 2019 13:40:04 -0400	[thread overview]
Message-ID: <85ef0eg6tn.fsf@collabora.com> (raw)

The following changes since commit e21a712a9685488f5ce80495b37b9fdbe96c230d:

  Linux 5.3-rc3 (2019-08-04 18:40:12 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git tags/unicode-next-v5.4

for you to fetch changes up to aa28b98d6dbcdb1c822b53f90e509565dfc450b0:

  unicode: make array 'token' static const, makes object smaller (2019-09-17 11:48:24 -0400)

----------------------------------------------------------------
fs/unicode patches for 5.4-rc1

This includes two fixes for the unicode system for inclusion into Linux
v5.4.

  - A patch from Krzysztof Wilczynski solving a build time warning.

  - A patch from Colin King making a parsing format static, to reduce
    stack size.

Build validated and run time tested using xfstests casefold testcase.

Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>

----------------------------------------------------------------
Colin Ian King (1):
      unicode: make array 'token' static const, makes object smaller

Krzysztof Wilczynski (1):
      unicode: Move static keyword to the front of declarations

 fs/unicode/utf8-core.c     | 2 +-
 fs/unicode/utf8-selftest.c | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
Gabriel Krisman Bertazi

                 reply	other threads:[~2019-09-17 17:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=85ef0eg6tn.fsf@collabora.com \
    --to=krisman@collabora.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).