From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: kbuild test robot <lkp@intel.com>
Cc: <kbuild-all@01.org>, <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matias Bjorling <mb@lightnvm.io>
Subject: Re: [PATCH 1/3] lightnvm: make core.c explicitly non-modular
Date: Sat, 29 Oct 2016 18:36:57 -0400 [thread overview]
Message-ID: <20161029223657.GL5641@windriver.com> (raw)
In-Reply-To: <201610300501.MjxoWVOy%fengguang.wu@intel.com>
[Re: [PATCH 1/3] lightnvm: make core.c explicitly non-modular] On 30/10/2016 (Sun 06:01) kbuild test robot wrote:
> Hi Paul,
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.9-rc3 next-20161028]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
As per the 0/3 mail, these commits are specific to Greg's char-misc
tree, and it was known they would fail on current "master".
> [Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
Does the above apply to _any_ tree on kernel.org? Or just commits
merged into mainline already? Since the base here is only in Greg's
repo and maybe also in some linux-next trees.
Thanks,
Paul.
--
> [Check https://git-scm.com/docs/git-format-patch for more information]
>
> url: https://github.com/0day-ci/linux/commits/Paul-Gortmaker/lightnvm-make-core-c-explicitly-non-modular/20161030-044459
> config: i386-randconfig-x073-201644 (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> >> drivers/lightnvm/core.c:1169:1: warning: data definition has no type or storage class
> builtin_misc_device(_nvm_misc);
> ^~~~~~~~~~~~~~~~~~~
> >> drivers/lightnvm/core.c:1169:1: error: type defaults to 'int' in declaration of 'builtin_misc_device' [-Werror=implicit-int]
> >> drivers/lightnvm/core.c:1169:1: warning: parameter names (without types) in function declaration
> >> drivers/lightnvm/core.c:1163:26: warning: '_nvm_misc' defined but not used [-Wunused-variable]
> static struct miscdevice _nvm_misc = {
> ^~~~~~~~~
> Cyclomatic Complexity 5 include/linux/compiler.h:__write_once_size
> Cyclomatic Complexity 1 arch/x86/include/asm/bitops.h:fls
> Cyclomatic Complexity 1 include/linux/log2.h:__ilog2_u32
> Cyclomatic Complexity 1 include/linux/list.h:__list_add
> Cyclomatic Complexity 1 include/linux/list.h:list_add
> Cyclomatic Complexity 1 include/linux/list.h:__list_del
> Cyclomatic Complexity 1 include/linux/list.h:list_del
> Cyclomatic Complexity 1 include/asm-generic/getorder.h:__get_order
> Cyclomatic Complexity 1 include/linux/spinlock.h:spinlock_check
> Cyclomatic Complexity 1 include/linux/slab.h:__kmalloc_node
> Cyclomatic Complexity 1 include/linux/slab.h:kmalloc_order_trace
> Cyclomatic Complexity 67 include/linux/slab.h:kmalloc_large
> Cyclomatic Complexity 3 include/linux/slab.h:kmalloc
> Cyclomatic Complexity 1 include/linux/slab.h:kmalloc_node
> Cyclomatic Complexity 1 include/linux/slab.h:kzalloc_node
> Cyclomatic Complexity 1 include/linux/lightnvm.h:generic_to_dev_addr
> Cyclomatic Complexity 1 include/linux/lightnvm.h:dev_to_generic_addr
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_dev_dma_alloc
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_dev_dma_free
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_get_blk
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_put_blk
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_mark_blk
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_submit_io
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_erase_blk
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_addr_to_generic_mode
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_generic_to_addr_mode
> Cyclomatic Complexity 2 drivers/lightnvm/core.c:nvm_free_rqd_ppalist
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_end_io
> Cyclomatic Complexity 5 drivers/lightnvm/core.c:nvm_bb_tbl_fold
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_get_bb_tbl
> Cyclomatic Complexity 2 drivers/lightnvm/core.c:nvm_free_mgr
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_alloc_dev
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_find_mgr_type
> Cyclomatic Complexity 5 drivers/lightnvm/core.c:nvm_find_target_type
> Cyclomatic Complexity 2 drivers/lightnvm/core.c:nvm_register_tgt_type
> Cyclomatic Complexity 2 drivers/lightnvm/core.c:nvm_unregister_tgt_type
> Cyclomatic Complexity 2 drivers/lightnvm/core.c:nvm_unregister_mgr
> Cyclomatic Complexity 3 include/linux/err.h:IS_ERR_OR_NULL
> Cyclomatic Complexity 8 drivers/lightnvm/core.c:nvm_init_mgr
> Cyclomatic Complexity 4 drivers/lightnvm/core.c:nvm_register_mgr
> Cyclomatic Complexity 9 drivers/lightnvm/core.c:nvm_set_rqd_ppalist
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_erase_ppa
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_end_io_sync
> Cyclomatic Complexity 1 include/linux/completion.h:init_completion
> Cyclomatic Complexity 5 drivers/lightnvm/core.c:__nvm_submit_ppa
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_submit_ppa_list
> Cyclomatic Complexity 2 drivers/lightnvm/core.c:nvm_submit_ppa
> Cyclomatic Complexity 5 include/linux/slab.h:kmalloc_array
> Cyclomatic Complexity 1 include/linux/slab.h:kcalloc
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_init_slc_tbl
> Cyclomatic Complexity 5 drivers/lightnvm/core.c:nvm_init_mlc_tbl
> Cyclomatic Complexity 9 drivers/lightnvm/core.c:nvm_core_init
> Cyclomatic Complexity 7 drivers/lightnvm/core.c:nvm_init
> Cyclomatic Complexity 10 drivers/lightnvm/core.c:nvm_register
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_exit
> Cyclomatic Complexity 1 drivers/lightnvm/core.c:nvm_unregister
> Cyclomatic Complexity 3 drivers/lightnvm/core.c:nvm_free
> cc1: some warnings being treated as errors
>
> vim +1169 drivers/lightnvm/core.c
>
> 1157 .open = nonseekable_open,
> 1158 .unlocked_ioctl = nvm_ctl_ioctl,
> 1159 .owner = THIS_MODULE,
> 1160 .llseek = noop_llseek,
> 1161 };
> 1162
> > 1163 static struct miscdevice _nvm_misc = {
> 1164 .minor = MISC_DYNAMIC_MINOR,
> 1165 .name = "lightnvm",
> 1166 .nodename = "lightnvm/control",
> 1167 .fops = &_ctl_fops,
> 1168 };
> > 1169 builtin_misc_device(_nvm_misc);
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2016-10-29 22:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 20:38 [PATCH 0/3] Add new builtin_misc_device users Paul Gortmaker
2016-10-29 20:38 ` Paul Gortmaker
2016-10-29 20:38 ` [PATCH 1/3] lightnvm: make core.c explicitly non-modular Paul Gortmaker
2016-10-29 22:01 ` kbuild test robot
2016-10-29 22:36 ` Paul Gortmaker [this message]
2016-10-29 20:38 ` [PATCH 2/3] blackfin: make-bf561/coreb.c " Paul Gortmaker
2016-10-30 1:02 ` kbuild test robot
2016-10-29 20:38 ` [PATCH 3/3] s390: char: make slp_ctl " Paul Gortmaker
2016-10-29 20:38 ` Paul Gortmaker
2016-10-29 22:49 ` kbuild test robot
2016-10-29 22:49 ` kbuild test robot
2016-10-30 13:43 ` Martin Schwidefsky
2016-10-30 13:43 ` Martin Schwidefsky
2016-10-30 16:04 ` Paul Gortmaker
2016-10-30 16:04 ` Paul Gortmaker
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=20161029223657.GL5641@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mb@lightnvm.io \
/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.