From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
David Sterba <dsterba@suse.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: trivial ->setattr cleanups
Date: Wed, 25 Mar 2026 07:36:47 +0100 [thread overview]
Message-ID: <20260325063711.3298685-1-hch@lst.de> (raw)
Hi all,
I've been looking into changes to ->setattr and noticed that we still
have a few instances where the method has the ages old notify_change
name. Fix this up and include dusting off outdated comments.
Diffstat:
adfs/adfs.h | 4 ++--
adfs/dir.c | 2 +-
adfs/file.c | 2 +-
adfs/inode.c | 6 ++----
affs/affs.h | 2 +-
affs/dir.c | 2 +-
affs/file.c | 2 +-
affs/inode.c | 5 ++---
affs/symlink.c | 2 +-
hfs/inode.c | 21 ++-------------------
proc/base.c | 22 +++++++++++-----------
proc/fd.c | 6 +++---
proc/generic.c | 8 ++++----
proc/internal.h | 4 ++--
proc/namespaces.c | 4 ++--
proc/proc_net.c | 2 +-
16 files changed, 37 insertions(+), 57 deletions(-)
next reply other threads:[~2026-03-25 6:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 6:36 Christoph Hellwig [this message]
2026-03-25 6:36 ` [PATCH 1/5] hfs: update comments on hfs_inode_setattr Christoph Hellwig
2026-03-25 11:52 ` Jan Kara
2026-03-25 16:38 ` vdubeyko
2026-03-25 6:36 ` [PATCH 2/5] adfs: rename adfs_notify_change to adfs_setattr Christoph Hellwig
2026-03-25 11:53 ` Jan Kara
2026-03-25 6:36 ` [PATCH 3/5] affs: rename affs_notify_change to affs_setattr Christoph Hellwig
2026-03-25 11:54 ` Jan Kara
2026-03-25 6:36 ` [PATCH 4/5] proc: rename proc_setattr to proc_nochmod_setattr Christoph Hellwig
2026-03-25 11:56 ` Jan Kara
2026-03-25 6:36 ` [PATCH 5/5] proc: rename proc_notify_change to proc_setattr Christoph Hellwig
2026-03-25 12:12 ` Jan Kara
2026-03-26 14:18 ` trivial ->setattr cleanups 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=20260325063711.3298685-1-hch@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
--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