[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180212182242.GP3003@twin.jikos.cz>
Date: Mon, 12 Feb 2018 19:22:42 +0100
From: David Sterba <dsterba@...e.cz>
To: Colin King <colin.king@...onical.com>
Cc: Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][btrfs-next] Btrfs: extent map selftest: fix non-ANSI
btrfs_test_extent_map declaration
On Thu, Feb 08, 2018 at 02:13:27PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> The function btrfs_test_extent_map requires a void argument to be ANSI C
> compliant and so it matches the prototype in fs/btrfs/tests/btrfs-tests.h
>
> Cleans up sparse warning:
> fs/btrfs/tests/extent-map-tests.c:346:27: warning: non-ANSI function
> declaration of function 'btrfs_test_extent_map'
>
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
FYI, the first patch fixing the warning has been added to for-next
already.
Powered by blists - more mailing lists