From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfsprogs for-next updated to 5f56a56
Date: Wed, 10 Oct 2018 17:41:37 +1100 [thread overview]
Message-ID: <20181010064137.GJ6311@dastard> (raw)
In-Reply-To: <e2306f09-8443-b05a-4f2a-d840ba8384d9@sandeen.net>
On Tue, Oct 09, 2018 at 05:55:01PM -0500, Eric Sandeen wrote:
> Hi folks,
>
> The for-next branch of the xfsprogs repository at:
>
> git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
>
> has just been updated.
>
> This update nukes the old unsupported/unloved platforms, fixes a bunch
> of sparse checker warnings (but not all), syncs a little bit more of
> 4.19's libxfs, includes 2 of djwong's libxfs cleanups, tidies up some
> mkfs behavior, and probably a couple other things. See below.
>
> Patches often get missed, so please check if your outstanding
> patches were in this update. If they have not been in this update,
> please resubmit them to linux-xfs@vger.kernel.org so they can be
> picked up in the next update.
>
> (I know there are still more outstanding patches on the list, will get
> to the ones I know about next, but feel free to resend if you like.)
>
> The new head of the for-next branch is commit:
>
> 5f56a56 libxfs: export unused nonstatic functions to quiet static checkers
>
> Thanks,
> -Eric
Just updated for for-next from 4.18.0, found some new warnings:
rdwr.c:548:1: warning: ¿libxfs_bprint¿ defined but not used [-Wunused-function]
libxfs_bprint(xfs_buf_t *bp)
^~~~~~~~~~~~~
util.c:384:1: warning: ¿libxfs_iprint¿ defined but not used [-Wunused-function]
libxfs_iprint(
^~~~~~~~~~~~~
.....
[CC] da_util.o
[CC] dinode.o
[CC] dir2.o
[LD] xfs_io
btree.c:448:1: warning: ¿btree_uncached_lookup¿ defined but not used [-Wunused-function]
btree_uncached_lookup(
^~~~~~~~~~~~~~~~~~~~~
And 'make deb' breaks because the version got changed in
convfigure.ac and the VERSION file, but the change logs in
doc/CHANGES weren't updated with ithe changes in 4.19.0-rc0....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-10-10 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 22:55 [ANNOUNCE] xfsprogs for-next updated to 5f56a56 Eric Sandeen
2018-10-10 6:41 ` Dave Chinner [this message]
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=20181010064137.GJ6311@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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.