From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-xfs@vger.kernel.org
Subject: Re: [xfs-linux:xfs-4.11-merge 38/39] fs/xfs/xfs_bmap_util.c:161:35: error: macro "xfs_rtallocate_extent" requires 9 arguments, but only 8 given
Date: Fri, 17 Feb 2017 20:50:35 -0800 [thread overview]
Message-ID: <20170218045035.GM6813@birch.djwong.org> (raw)
In-Reply-To: <201702181018.SEkBmT5z%fengguang.wu@intel.com>
On Sat, Feb 18, 2017 at 10:47:19AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git xfs-4.11-merge
> head: c7016e9a73f1f8a8a21a8fdfc84f556fb8f14583
> commit: ec48023e05afbd7e04269306b814bcaf86e1e047 [38/39] xfs: simplify xfs_rtallocate_extent
> config: i386-randconfig-x006-201707 (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> git checkout ec48023e05afbd7e04269306b814bcaf86e1e047
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> fs/xfs/xfs_bmap_util.c: In function 'xfs_bmap_rtalloc':
> >> fs/xfs/xfs_bmap_util.c:161:35: error: macro "xfs_rtallocate_extent" requires 9 arguments, but only 8 given
> &ralen, ap->wasdel, prod, &rtb);
Bleh, I fixed the patch and pushed out a new branch.
--D
> ^
> >> fs/xfs/xfs_bmap_util.c:160:10: error: 'xfs_rtallocate_extent' undeclared (first use in this function)
> error = xfs_rtallocate_extent(ap->tp, ap->blkno, 1, ap->length,
> ^~~~~~~~~~~~~~~~~~~~~
> fs/xfs/xfs_bmap_util.c:160:10: note: each undeclared identifier is reported only once for each function it appears in
>
> vim +/xfs_rtallocate_extent +161 fs/xfs/xfs_bmap_util.c
>
> 154 /*
> 155 * Realtime allocation, done through xfs_rtallocate_extent.
> 156 */
> 157 do_div(ap->blkno, mp->m_sb.sb_rextsize);
> 158 rtb = ap->blkno;
> 159 ap->length = ralen;
> > 160 error = xfs_rtallocate_extent(ap->tp, ap->blkno, 1, ap->length,
> > 161 &ralen, ap->wasdel, prod, &rtb);
> 162 if (error)
> 163 return error;
> 164
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
prev parent reply other threads:[~2017-02-18 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 2:47 [xfs-linux:xfs-4.11-merge 38/39] fs/xfs/xfs_bmap_util.c:161:35: error: macro "xfs_rtallocate_extent" requires 9 arguments, but only 8 given kbuild test robot
2017-02-18 4:50 ` Darrick J. Wong [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=20170218045035.GM6813@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-xfs@vger.kernel.org \
/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).