From: "André Almeida" <andrealmeid@igalia.com>
To: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
krisman@kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>,
Nathan Chancellor <nathan@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, kernel-dev@igalia.com,
"Theodore Ts'o" <tytso@mit.edu>,
"André Almeida" <andrealmeid@igalia.com>
Subject: [PATCH v2 0/3] tmpfs: Casefold fixes
Date: Fri, 1 Nov 2024 13:42:48 -0300 [thread overview]
Message-ID: <20241101164251.327884-1-andrealmeid@igalia.com> (raw)
After casefold support for tmpfs was merged into vfs tree, two warnings
were reported and I also found a small fix in the code.
Thanks Nathan Chancellor and Stephen Rothwell!
Changelog:
- Fixed ifdef guard for tmpfs_sysfs_init()
v1: https://lore.kernel.org/lkml/20241101013741.295792-1-andrealmeid@igalia.com/
André Almeida (3):
libfs: Fix kernel-doc warning in generic_ci_validate_strict_name
tmpfs: Fix type for sysfs' casefold attribute
tmpfs: Initialize sysfs during tmpfs init
include/linux/fs.h | 10 ++---
mm/shmem.c | 105 +++++++++++++++++++++++++++++----------------
2 files changed, 73 insertions(+), 42 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-01 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 16:42 André Almeida [this message]
2024-11-01 16:42 ` [PATCH v2 1/3] libfs: Fix kernel-doc warning in generic_ci_validate_strict_name André Almeida
2024-11-01 16:42 ` [PATCH v2 2/3] tmpfs: Fix type for sysfs' casefold attribute André Almeida
2024-11-01 16:42 ` [PATCH v2 3/3] tmpfs: Initialize sysfs during tmpfs init André Almeida
2024-11-06 10:23 ` [PATCH v2 0/3] tmpfs: Casefold fixes Christian Brauner
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=20241101164251.327884-1-andrealmeid@igalia.com \
--to=andrealmeid@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kernel-dev@igalia.com \
--cc=krisman@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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