[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250803102243.623705-1-rongqianfeng@vivo.com>
Date: Sun, 3 Aug 2025 18:22:38 +0800
From: Qianfeng Rong <rongqianfeng@...o.com>
To: Kent Overstreet <kent.overstreet@...ux.dev>,
Eric Biggers <ebiggers@...nel.org>,
"Theodore Y. Ts'o" <tytso@....edu>,
Jaegeuk Kim <jaegeuk@...nel.org>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Jan Kara <jack@...e.cz>,
linux-bcachefs@...r.kernel.org (open list:BCACHEFS),
linux-kernel@...r.kernel.org (open list),
linux-fscrypt@...r.kernel.org (open list:FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT),
linux-ext4@...r.kernel.org (open list:EXT4 FILE SYSTEM),
linux-fsdevel@...r.kernel.org (open list:FILESYSTEMS (VFS and infrastructure))
Cc: willy@...radead.org,
Qianfeng Rong <rongqianfeng@...o.com>
Subject: [PATCH 0/4] fs: Remove redundant __GFP_NOWARN
Commit 16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT")
made GFP_NOWAIT implicitly include __GFP_NOWARN.
Therefore, explicit __GFP_NOWARN combined with GFP_NOWAIT
(e.g., `GFP_NOWAIT | __GFP_NOWARN`) is now redundant. Let's clean
up these redundant flags across subsystems.
No functional changes.
Qianfeng Rong (4):
bcachefs: Remove redundant __GFP_NOWARN
fscrypto: Remove redundant __GFP_NOWARN
ext4: Remove redundant __GFP_NOWARN
fs-writeback: Remove redundant __GFP_NOWARN
fs/bcachefs/btree_cache.c | 4 ++--
fs/bcachefs/btree_io.c | 2 +-
fs/bcachefs/btree_iter.h | 6 +++---
fs/bcachefs/btree_trans_commit.c | 2 +-
fs/bcachefs/fs.c | 2 +-
fs/crypto/bio.c | 2 +-
fs/ext4/page-io.c | 2 +-
fs/ext4/super.c | 2 +-
fs/fs-writeback.c | 2 +-
9 files changed, 12 insertions(+), 12 deletions(-)
--
2.34.1
Powered by blists - more mailing lists