From: "Theodore Ts'o" <tytso@mit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>, linux-mm@kvack.org
Subject: Re: [PATCH -v3] mm/shmem: support FS_IOC_[SG]ETFLAGS in tmpfs
Date: Wed, 20 Jul 2022 07:10:04 -0400 [thread overview]
Message-ID: <YtfijJjDjzEcBAku@mit.edu> (raw)
In-Reply-To: <20220715015912.2560575-1-tytso@mit.edu>
On Thu, Jul 14, 2022 at 09:59:12PM -0400, Theodore Ts'o wrote:
> This allows userspace to set flags like FS_APPEND_FL, FS_IMMUTABLE_FL,
> FS_NODUMP_FL, etc., like all other standard Linux file systems.
>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Hi Andrew,
I notice that in your most recent mm-unstable tree, you still have the
v1 version of the patch plus your fixup:
* c523739526b3 - mm/shmem: support FS_IOC_[SG]ETFLAGS in tmpfs (6 hours ago)
* 2d6c68e33857 - mm-shmem-support-fs_ioc_etflags-in-tmpfs-fix (6 hours ago)
Could you please replace these two patches with the v3 version of the
patch at:
https://lore.kernel.org/all/20220715015912.2560575-1-tytso@mit.edu/
There haven't been any other comments in the past week, so I'm hopeful
this will be the final version of this proposed change.
Many thanks!
- Ted
next prev parent reply other threads:[~2022-07-20 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:52 [PATCH] mm/shmem: add support for FS_IOC_[SG]ETFLAGS for tmpfs Theodore Ts'o
2022-07-13 19:11 ` Andrew Morton
2022-07-14 1:40 ` Theodore Ts'o
2022-07-14 2:24 ` [PATCH -v2] mm/shmem: support FS_IOC_[SG]ETFLAGS in tmpfs Theodore Ts'o
2022-07-15 1:59 ` [PATCH -v3] " Theodore Ts'o
2022-07-20 11:10 ` Theodore Ts'o [this message]
2022-07-20 16:59 ` Andrew Morton
2022-08-11 4:44 ` Hugh Dickins
2022-07-14 23:01 ` [PATCH] mm/shmem: add support for FS_IOC_[SG]ETFLAGS for tmpfs kernel test robot
2022-07-15 11:09 ` Arnd Bergmann
2022-07-15 11:36 ` Theodore Ts'o
2022-07-14 23:11 ` 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=YtfijJjDjzEcBAku@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.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).