From: John Hubbard <jhubbard@nvidia.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
<linux-xfs@vger.kernel.org>,
Linux Next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Brian Foster <bfoster@redhat.com>, Christoph Hellwig <hch@lst.de>,
Allison Henderson <allison.henderson@oracle.com>
Subject: Re: [PATCH] xfs: fix unused variable build warning in xfs_log.c
Date: Thu, 4 Feb 2021 19:49:54 -0800 [thread overview]
Message-ID: <11a20ea7-3d58-d102-0fcb-6bc92cfc86d5@nvidia.com> (raw)
In-Reply-To: <20210205033030.GL7193@magnolia>
On 2/4/21 7:30 PM, Darrick J. Wong wrote:
> On Thu, Feb 04, 2021 at 07:18:14PM -0800, John Hubbard wrote:
>> 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 for the tipoff, I just realized with horror that I got the git
> push wrong and never actually updated xfs-linux.git#for-next. This (and
> all the other gcc warnings) are fixed in "xfs-for-next" which ... is not
> for-next.
>
> Sigh..... so much for trying to get things in for testing. :(
>
Well, if it's any consolation, this is the *only* warning that fired during
my particular build, in linux-next. :)
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2021-02-05 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 3:18 [PATCH] xfs: fix unused variable build warning in xfs_log.c John Hubbard
2021-02-05 3:30 ` Darrick J. Wong
2021-02-05 3:49 ` John Hubbard [this message]
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=11a20ea7-3d58-d102-0fcb-6bc92cfc86d5@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