From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Steve French <sfrench@samba.org>,
linux-afs@lists.infradead.org, linux-cifs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] Make folio_start_writeback return void
Date: Wed, 8 Nov 2023 20:46:01 +0000 [thread overview]
Message-ID: <20231108204605.745109-1-willy@infradead.org> (raw)
Most of the folio flag-setting functions return void.
folio_start_writeback is gratuitously different; the only two filesystems
that do anything with the return value emit debug messages if it's already
set, and we can (and should) do that internally without bothering the
filesystem to do it.
Matthew Wilcox (Oracle) (4):
mm: Remove test_set_page_writeback()
afs: Do not test the return value of folio_start_writeback()
smb: Do not test the return value of folio_start_writeback()
mm: Return void from folio_start_writeback() and related functions
fs/afs/write.c | 6 ++---
fs/smb/client/file.c | 6 ++---
include/linux/page-flags.h | 9 ++-----
mm/folio-compat.c | 4 +--
mm/page-writeback.c | 54 ++++++++++++++++++--------------------
5 files changed, 33 insertions(+), 46 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-08 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 20:46 Matthew Wilcox (Oracle) [this message]
2023-11-08 20:46 ` [PATCH 1/4] mm: Remove test_set_page_writeback() Matthew Wilcox (Oracle)
2023-11-08 20:46 ` [PATCH 2/4] afs: Do not test the return value of folio_start_writeback() Matthew Wilcox (Oracle)
2023-11-08 20:46 ` [PATCH 3/4] smb: " Matthew Wilcox (Oracle)
2023-11-09 3:46 ` Paulo Alcantara
2023-11-09 4:33 ` Steve French
2023-11-08 20:46 ` [PATCH 4/4] mm: Return void from folio_start_writeback() and related functions Matthew Wilcox (Oracle)
2023-11-17 19:22 ` Josef Bacik
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=20231108204605.745109-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfrench@samba.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).