From: Anand Jain <anand.jain@oracle.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: rename btrfs_close_extra_device to btrfs_free_extra_devids
Date: Sat, 3 Mar 2018 19:03:35 +0800 [thread overview]
Message-ID: <c12e47db-6a5e-3f88-6f05-3fe916dd6877@oracle.com> (raw)
In-Reply-To: <201803011216.UCOGFQ7a%fengguang.wu@intel.com>
On 03/01/2018 12:42 PM, kbuild test robot wrote:
> Hi Anand,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on btrfs/next]
> [also build test ERROR on v4.16-rc3 next-20180228]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
Should use v2 in the ML.
[PATCH v2] btrfs: rename btrfs_close_extra_device to
btrfs_free_extra_devids
Thanks, Anand
> url: https://github.com/0day-ci/linux/commits/Anand-Jain/btrfs-rename-btrfs_close_extra_device-to-btrfs_free_extra_devids/20180301-120850
> base: https://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next
> config: x86_64-randconfig-x016-201808 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> fs/btrfs/disk-io.c: In function 'open_ctree':
>>> fs/btrfs/disk-io.c:2783:2: error: implicit declaration of function 'btrfs_free_extra_devids'; did you mean 'btrfs_free_extra_devid'? [-Werror=implicit-function-declaration]
> btrfs_free_extra_devids(fs_devices, 0);
> ^~~~~~~~~~~~~~~~~~~~~~~
> btrfs_free_extra_devid
> cc1: some warnings being treated as errors
prev parent reply other threads:[~2018-03-03 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 4:32 [PATCH] btrfs: rename btrfs_close_extra_device to btrfs_free_extra_devids Anand Jain
2018-02-27 4:41 ` [PATCH v2] " Anand Jain
2018-03-05 21:28 ` David Sterba
2018-03-01 4:42 ` [PATCH] " kbuild test robot
2018-03-01 6:16 ` Anand Jain
2018-03-03 11:03 ` Anand Jain [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=c12e47db-6a5e-3f88-6f05-3fe916dd6877@oracle.com \
--to=anand.jain@oracle.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
/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).