linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the xfs tree
Date: Thu, 23 Jan 2020 20:17:43 -0800	[thread overview]
Message-ID: <20200124041743.GU8257@magnolia> (raw)
In-Reply-To: <20200124134722.728032e6@canb.auug.org.au>

On Fri, Jan 24, 2020 at 01:47:22PM +1100, Stephen Rothwell wrote:
> Hi all
> 
> On Thu, 16 Jan 2020 09:12:42 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the xfs tree, today's linux-next build
> > (powerpppc64_defconfig) produced this warning:
> > 
> > fs/xfs/xfs_inode.c: In function 'xfs_itruncate_extents_flags':
> > fs/xfs/xfs_inode.c:1523:8: warning: unused variable 'done' [-Wunused-variable]
> >  1523 |  int   done = 0;
> >       |        ^~~~
> > 
> > Introduced by commit
> > 
> >   4bbb04abb4ee ("xfs: truncate should remove all blocks, not just to the end of the page cache")
> 
> I am still getting this warning.

Aha, I had though this was gone but it turns out that I accidentally
merged the fix for this into an internal patch to grease my internal CI
scripts.  Ah well.  Patch soon.

--D

> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2020-01-24  4:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 22:12 linux-next: build warning after merge of the xfs tree Stephen Rothwell
2020-01-24  2:47 ` Stephen Rothwell
2020-01-24  4:17   ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23  4:36 Stephen Rothwell
2024-02-23  6:35 ` Christoph Hellwig
2024-02-23  8:55   ` Mauro Carvalho Chehab
2024-02-23 14:06     ` Christoph Hellwig
2024-02-24  9:07       ` Akira Yokosawa
2024-02-26 10:57         ` Christoph Hellwig
2021-06-07  0:48 Stephen Rothwell
2021-06-07  1:15 ` Dave Chinner
2021-02-08 12:44 Stephen Rothwell
2021-01-24 22:55 Stephen Rothwell
2021-01-25 13:26 ` Brian Foster
2021-01-27  3:14   ` Darrick J. Wong
2020-05-08  1:15 Stephen Rothwell
2020-01-16  0:37 Stephen Rothwell
2017-10-31 22:42 Stephen Rothwell
2017-08-31  0:07 Stephen Rothwell
2017-08-31 10:30 ` Brian Foster
2017-08-31 14:57   ` Darrick J. Wong
2017-08-31 15:22     ` Brian Foster
2017-08-31 15:41       ` Darrick J. Wong
2017-08-31 21:32       ` Dave Chinner
2010-03-04  0:19 Stephen Rothwell

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=20200124041743.GU8257@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --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;
as well as URLs for NNTP newsgroup(s).