mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2019.03.20b 54/83] drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:50:1: error: type defaults to 'int' in declaration of 'DEFINE_SRCU'
Date: Mon, 25 Mar 2019 02:34:27 +0800	[thread overview]
Message-ID: <201903250225.RRMwkT3f%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.03.20b
head:   6d4434b4b4df791620743178e1419de882b44c7b
commit: eb89abcb30733e3a2343dda23cb6d81cc17c60b3 [54/83] rcu: Forbid DEFINE{,_STATIC}_SRCU() from modules
config: x86_64-randconfig-b0-03250021 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout eb89abcb30733e3a2343dda23cb6d81cc17c60b3
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:50:1: warning: data definition has no type or storage class
    DEFINE_SRCU(kfd_processes_srcu);
    ^~~~~~~~~~~
>> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:50:1: error: type defaults to 'int' in declaration of 'DEFINE_SRCU' [-Werror=implicit-int]
   drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:50:1: warning: parameter names (without types) in function declaration
   cc1: some warnings being treated as errors

vim +50 drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c

19f6d2a6 Oded Gabbay    2014-07-16  49  
64d1c3a4 Felix Kuehling 2017-12-08 @50  DEFINE_SRCU(kfd_processes_srcu);
19f6d2a6 Oded Gabbay    2014-07-16  51  

:::::: The code at line 50 was first introduced by commit
:::::: 64d1c3a43a6fb5cef32a085bc17cbbe31945a651 drm/amdkfd: Centralize IOMMUv2 code and make it conditional

:::::: TO: Felix Kuehling <Felix.Kuehling@amd.com>
:::::: CC: Oded Gabbay <oded.gabbay@gmail.com>

---
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: 25237 bytes --]

             reply	other threads:[~2019-03-24 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 18:34 kbuild test robot [this message]
2019-03-27 19:57 ` Paul E. McKenney
2019-04-02  0:32   ` Rong Chen
2019-04-02 13:04     ` Paul E. McKenney
2019-04-02 13:50       ` Rong Chen
2019-04-02 14:16         ` Paul E. McKenney

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=201903250225.RRMwkT3f%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.ibm.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

Powered by JetHome