From: kernel test robot <lkp@intel.com>
To: Umang Parekh <umang.parekh@xilinx.com>
Cc: Sonal Santan <sonal.santan@xilinx.com>,
Michal Simek <monstr@monstr.eu>,
kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [xlnx:xlnx_rebase_v5.4 179/1683] include/uapi/linux/zocl_ioctl.h:43:2: error: unknown type name 'uint32_t'
Date: Sun, 1 Nov 2020 22:50:21 +0800 [thread overview]
Message-ID: <202011012215.7caWiM3x-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4186 bytes --]
Hi Umang,
FYI, the error/warning still remains.
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v5.4
head: 87d2d58e2137748748d96a630fd93eb0e2d81123
commit: f4c3b72e2c97c5350214853d0e9fbd93e2cea071 [179/1683] drm: ZynQ OpenCL driver
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/Xilinx/linux-xlnx/commit/f4c3b72e2c97c5350214853d0e9fbd93e2cea071
git remote add xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xlnx xlnx_rebase_v5.4
git checkout f4c3b72e2c97c5350214853d0e9fbd93e2cea071
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:
include/uapi/linux/zocl_ioctl.h:42:2: error: unknown type name 'uint64_t'
42 | uint64_t size;
| ^~~~~~~~
>> include/uapi/linux/zocl_ioctl.h:43:2: error: unknown type name 'uint32_t'
43 | uint32_t handle;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:44:2: error: unknown type name 'uint32_t'
44 | uint32_t flags;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:48:2: error: unknown type name 'uint32_t'
48 | uint32_t handle;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:49:2: error: unknown type name 'uint32_t'
49 | uint32_t pad;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:50:2: error: unknown type name 'uint64_t'
50 | uint64_t offset;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:61:2: error: unknown type name 'uint32_t'
61 | uint32_t handle;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:63:2: error: unknown type name 'uint64_t'
63 | uint64_t offset;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:64:2: error: unknown type name 'uint64_t'
64 | uint64_t size;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:74:2: error: unknown type name 'uint32_t'
74 | uint32_t handle;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:75:2: error: unknown type name 'uint64_t'
75 | uint64_t size;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:76:2: error: unknown type name 'uint64_t'
76 | uint64_t paddr;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:88:2: error: unknown type name 'uint32_t'
88 | uint32_t handle;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:89:2: error: unknown type name 'uint32_t'
89 | uint32_t pad;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:90:2: error: unknown type name 'uint64_t'
90 | uint64_t offset;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:91:2: error: unknown type name 'uint64_t'
91 | uint64_t size;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:92:2: error: unknown type name 'uint64_t'
92 | uint64_t data_ptr;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:104:2: error: unknown type name 'uint32_t'
104 | uint32_t handle;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:105:2: error: unknown type name 'uint32_t'
105 | uint32_t pad;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:106:2: error: unknown type name 'uint64_t'
106 | uint64_t offset;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:107:2: error: unknown type name 'uint64_t'
107 | uint64_t size;
| ^~~~~~~~
include/uapi/linux/zocl_ioctl.h:108:2: error: unknown type name 'uint64_t'
108 | uint64_t data_ptr;
| ^~~~~~~~
vim +/uint32_t +43 include/uapi/linux/zocl_ioctl.h
40
41 struct drm_zocl_create_bo {
42 uint64_t size;
> 43 uint32_t handle;
44 uint32_t flags;
45 };
46
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 51767 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-11-01 14:52 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=202011012215.7caWiM3x-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=monstr@monstr.eu \
--cc=sonal.santan@xilinx.com \
--cc=umang.parekh@xilinx.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;
as well as URLs for NNTP newsgroup(s).