All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-rt-devel:linux-5.4.y-rt 147/261] arch/riscv/include/asm/spinlock_types.h:10:3: error: #error "please don't include this file directly"
Date: Sat, 04 Jan 2020 20:17:00 +0800	[thread overview]
Message-ID: <202001042054.m8TzNAKG%lkp@intel.com> (raw)

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

Hi Thomas,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-5.4.y-rt
head:   1fbcaa9506f953b1f054c0d1ae79776fb77887b3
commit: 61ff0ce6f914fabe3129f2b35a30b8f65c7c39b5 [147/261] spinlock: Split the lock types header
config: riscv-allmodconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 61ff0ce6f914fabe3129f2b35a30b8f65c7c39b5
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=riscv 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from include/linux/spinlock_types_raw.h:7:0,
                    from <command-line>:0:
>> arch/riscv/include/asm/spinlock_types.h:10:3: error: #error "please don't include this file directly"
    # error "please don't include this file directly"
      ^~~~~

vim +10 arch/riscv/include/asm/spinlock_types.h

fab957c11efe2f Palmer Dabbelt 2017-07-10   8  
fab957c11efe2f Palmer Dabbelt 2017-07-10   9  #ifndef __LINUX_SPINLOCK_TYPES_H
fab957c11efe2f Palmer Dabbelt 2017-07-10 @10  # error "please don't include this file directly"
fab957c11efe2f Palmer Dabbelt 2017-07-10  11  #endif
fab957c11efe2f Palmer Dabbelt 2017-07-10  12  

:::::: The code at line 10 was first introduced by commit
:::::: fab957c11efe2f405e08b9f0d080524bc2631428 RISC-V: Atomic and Locking Code

:::::: TO: Palmer Dabbelt <palmer@dabbelt.com>
:::::: CC: Palmer Dabbelt <palmer@dabbelt.com>

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 59999 bytes --]

                 reply	other threads:[~2020-01-04 12:17 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=202001042054.m8TzNAKG%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.