From: kbuild test robot <fengguang.wu@intel.com>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 2814/2850] lib/radix-tree.c:1947:3: error: too few arguments to function '__radix_tree_delete_node'
Date: Tue, 10 Jan 2017 19:34:11 +0800 [thread overview]
Message-ID: <201701101947.a1DqdYFX%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7a399e4b4bf5368a43427bdc7541655702aced47
commit: fa06219c337a2822fc969dd68cfa93e1d244283b [2814/2850] Reimplement IDR and IDA using the radix tree
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout fa06219c337a2822fc969dd68cfa93e1d244283b
# save the attached .config to linux build tree
make ARCH=i386
Note: the linux-next/master HEAD 7a399e4b4bf5368a43427bdc7541655702aced47 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
lib/radix-tree.c: In function 'radix_tree_iter_delete':
>> lib/radix-tree.c:1947:3: error: too few arguments to function '__radix_tree_delete_node'
__radix_tree_delete_node(root, node);
^~~~~~~~~~~~~~~~~~~~~~~~
lib/radix-tree.c:1931:6: note: declared here
void __radix_tree_delete_node(struct radix_tree_root *root,
^~~~~~~~~~~~~~~~~~~~~~~~
vim +/__radix_tree_delete_node +1947 lib/radix-tree.c
1941 {
1942 struct radix_tree_node *node = iter->node;
1943
1944 if (node) {
1945 node->slots[iter_offset(iter)] = NULL;
1946 node->count--;
> 1947 __radix_tree_delete_node(root, node);
1948 } else {
1949 root->rnode = NULL;
1950 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6420 bytes --]
reply other threads:[~2017-01-10 11:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201701101947.a1DqdYFX%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=willy@linux.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