From: John Hubbard <jhubbard@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-xfs@vger.kernel.org>,
Linux Next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>,
"Brian Foster" <bfoster@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>,
Allison Henderson <allison.henderson@oracle.com>
Subject: [PATCH] xfs: fix unused variable build warning in xfs_log.c
Date: Thu, 4 Feb 2021 19:18:14 -0800 [thread overview]
Message-ID: <20210205031814.414649-1-jhubbard@nvidia.com> (raw)
Delete the unused "log" variable in xfs_log_cover().
Fixes: 303591a0a9473 ("xfs: cover the log during log quiesce")
Cc: Brian Foster <bfoster@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Darrick J. Wong <djwong@kernel.org>
Cc: Allison Henderson <allison.henderson@oracle.com>
Signed-off-by: John Hubbard <jhubbard@nvidia.com>
---
Hi,
I just ran into this on today's linux-next, so here you go!
thanks,
John Hubbard
NVIDIA
fs/xfs/xfs_log.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
index 58699881c100..5a9cca3f7cbf 100644
--- a/fs/xfs/xfs_log.c
+++ b/fs/xfs/xfs_log.c
@@ -1108,7 +1108,6 @@ static int
xfs_log_cover(
struct xfs_mount *mp)
{
- struct xlog *log = mp->m_log;
int error = 0;
bool need_covered;
base-commit: 0e2c50f40b7ffb73a039157f7c38495c6d99e86f
--
2.30.0
next reply other threads:[~2021-02-05 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 3:18 John Hubbard [this message]
2021-02-05 3:30 ` [PATCH] xfs: fix unused variable build warning in xfs_log.c Darrick J. Wong
2021-02-05 3:49 ` John Hubbard
2021-02-05 3:58 ` Chaitanya Kulkarni
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=20210205031814.414649-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=allison.henderson@oracle.com \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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