From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [leon-rdma:rdma-next 41/42] drivers/infiniband/hw/hfi1/init.c:1865: warning: expecting prototype for ahfi1_setup_eagerbufs(). Prototype was for hfi1_setup_eagerbufs() instead
Date: Fri, 12 Mar 2021 06:40:27 +0800 [thread overview]
Message-ID: <202103120618.H2h0ql7w-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3076 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git rdma-next
head: 05f9b877d9328976740745c6f5451a83685920d6
commit: 8a9792233781a714da6cecba33b693bcabfc4b31 [41/42] RDMA: Fix kernel-doc compilation warnings
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/commit/?id=8a9792233781a714da6cecba33b693bcabfc4b31
git remote add leon-rdma https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
git fetch --no-tags leon-rdma rdma-next
git checkout 8a9792233781a714da6cecba33b693bcabfc4b31
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/infiniband/hw/hfi1/init.c:1865: warning: expecting prototype for ahfi1_setup_eagerbufs(). Prototype was for hfi1_setup_eagerbufs() instead
vim +1865 drivers/infiniband/hw/hfi1/init.c
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1853
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1854 /**
8a9792233781a7 drivers/infiniband/hw/hfi1/init.c Leon Romanovsky 2021-03-11 1855 * ahfi1_setup_eagerbufs - llocate eager buffers, both kernel and user
8a9792233781a7 drivers/infiniband/hw/hfi1/init.c Leon Romanovsky 2021-03-11 1856 * contexts.
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1857 * @rcd: the context we are setting up.
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1858 *
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1859 * Allocate the eager TID buffers and program them into hip.
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1860 * They are no longer completely contiguous, we do multiple allocation
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1861 * calls. Otherwise we get the OOM code involved, by asking for too
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1862 * much per call, with disastrous results on some kernels.
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1863 */
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 1864 int hfi1_setup_eagerbufs(struct hfi1_ctxtdata *rcd)
7724105686e718 drivers/staging/rdma/hfi1/init.c Mike Marciniszyn 2015-07-30 @1865 {
:::::: The code at line 1865 was first introduced by commit
:::::: 7724105686e718ac476a6ad3304fea2fbcfcffde IB/hfi1: add driver files
:::::: TO: Mike Marciniszyn <mike.marciniszyn@intel.com>
:::::: CC: Doug Ledford <dledford@redhat.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65039 bytes --]
reply other threads:[~2021-03-11 22:40 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=202103120618.H2h0ql7w-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.