From: kernel test robot <lkp@intel.com>
To: Olivier Masse <olivier.masse@nxp.com>,
jens.wiklander@linaro.org, sumit.garg@linaro.org,
sumit.semwal@linaro.org, christian.koenig@amd.com,
op-tee@lists.trustedfirmware.org, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, clement.faure@nxp.com, olivier.masse@nxp.com
Subject: Re: [PATCH 1/1] tee: new ioctl to a register tee_shm from a dmabuf file descriptor
Date: Fri, 12 Aug 2022 13:27:13 +0800 [thread overview]
Message-ID: <202208121326.FWVAzlch-lkp@intel.com> (raw)
In-Reply-To: <20220811135637.6332-2-olivier.masse@nxp.com>
Hi Olivier,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-tip/drm-tip linus/master v5.19 next-20220811]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Olivier-Masse/tee-Add-tee_shm_register_fd/20220811-220012
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220812/202208121326.FWVAzlch-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/2e8827973f200fdfe64366bec5a57686086f4672
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Olivier-Masse/tee-Add-tee_shm_register_fd/20220811-220012
git checkout 2e8827973f200fdfe64366bec5a57686086f4672
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:
>> ./usr/include/linux/tee.h:136:13: error: expected declaration specifiers or '...' before numeric constant
136 | } __aligned(8);
| ^
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-08-12 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 13:56 [PATCH 0/1] tee: Add tee_shm_register_fd Olivier Masse
2022-08-11 13:56 ` [PATCH 1/1] tee: new ioctl to a register tee_shm from a dmabuf file descriptor Olivier Masse
2022-08-12 5:27 ` kernel test robot [this message]
2022-08-12 10:18 ` Christian König
2022-08-12 13:24 ` [EXT] " Olivier Masse
2022-08-12 14:06 ` Sumit Garg
2022-08-12 14:23 ` [EXT] " Olivier Masse
2022-08-12 14:01 ` [PATCH 0/1] tee: Add tee_shm_register_fd Sumit Garg
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 14:30 [PATCH v2 " Olivier Masse
2022-08-12 14:30 ` [PATCH 1/1] tee: new ioctl to a register tee_shm from a dmabuf file descriptor Olivier Masse
2022-08-14 1:13 ` kernel test robot
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=202208121326.FWVAzlch-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.koenig@amd.com \
--cc=clement.faure@nxp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jens.wiklander@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=olivier.masse@nxp.com \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@linaro.org \
--cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox