From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, anton@tuxera.com, zhengzengkai@huawei.com
Subject: [alternative-merged] fs-ntfs-fix-set-but-not-used-variable-log_page_mask.patch removed from -mm tree
Date: Wed, 09 Dec 2020 18:36:42 -0800 [thread overview]
Message-ID: <20201210023642.xotj9%akpm@linux-foundation.org> (raw)
The patch titled
Subject: fs/ntfs: fix set but not used variable 'log_page_mask'
has been removed from the -mm tree. Its filename was
fs-ntfs-fix-set-but-not-used-variable-log_page_mask.patch
This patch was dropped because an alternative patch was merged
------------------------------------------------------
From: Zheng Zengkai <zhengzengkai@huawei.com>
Subject: fs/ntfs: fix set but not used variable 'log_page_mask'
Fixes gcc '-Wunused-but-set-variable' warning:
fs/ntfs/logfile.c: In function ntfs_check_logfile:
fs/ntfs/logfile.c:481:21:
warning: variable log_page_mask set but not used [-Wunused-but-set-variable]
Actually log_page_mask can be used to replace 'log_page_size - 1' as it is set.
Link: https://lkml.kernel.org/r/20200312041353.19877-1-zhengzengkai@huawei.com
Signed-off-by: Zheng Zengkai <zhengzengkai@huawei.com>
Acked-by: Anton Altaparmakov <anton@tuxera.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/ntfs/logfile.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/ntfs/logfile.c~fs-ntfs-fix-set-but-not-used-variable-log_page_mask
+++ a/fs/ntfs/logfile.c
@@ -506,7 +506,7 @@ bool ntfs_check_logfile(struct inode *lo
* optimize log_page_size and log_page_bits into constants.
*/
log_page_bits = ntfs_ffs(log_page_size) - 1;
- size &= ~(s64)(log_page_size - 1);
+ size &= ~(s64)(log_page_mask);
/*
* Ensure the log file is big enough to store at least the two restart
* pages and the minimum number of log record pages.
_
Patches currently in -mm which might be from zhengzengkai@huawei.com are
reply other threads:[~2020-12-10 2:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201210023642.xotj9%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anton@tuxera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=zhengzengkai@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.