From: kernel test robot <lkp@intel.com>
To: Nirmoy Das <nirmoy.das@amd.com>, dri-devel@lists.freedesktop.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
intel-gfx@lists.freedesktop.org, Nirmoy Das <nirmoy.das@amd.com>,
Russell King <linux@armlinux.org.uk>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 4/5] drm/armada: check dri/crtc root before debugfs init
Date: Wed, 13 Oct 2021 03:40:24 +0800 [thread overview]
Message-ID: <202110130358.vZd7yOQ1-lkp@intel.com> (raw)
In-Reply-To: <20211008091704.27094-4-nirmoy.das@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]
Hi Nirmoy,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on tegra/for-next drm-tip/drm-tip linus/master v5.15-rc5 next-20211012]
[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]
url: https://github.com/0day-ci/linux/commits/Nirmoy-Das/dri-cleanup-debugfs-error-handling/20211008-173312
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: arm-randconfig-r034-20211012 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c3dcf39554dbea780d6cb7e12239451ba47a2668)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://github.com/0day-ci/linux/commit/0c9a39f1265783134650d360585c60e0b1f64efe
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Nirmoy-Das/dri-cleanup-debugfs-error-handling/20211008-173312
git checkout 0c9a39f1265783134650d360585c60e0b1f64efe
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm
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 >>):
>> drivers/gpu/drm/armada/armada_debugfs.c:111:3: error: non-void function 'armada_drm_debugfs_init' should return a value [-Wreturn-type]
return;
^
1 error generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for QCOM_SCM
Depends on (ARM || ARM64) && HAVE_ARM_SMCCC
Selected by
- ARM_QCOM_SPM_CPUIDLE && CPU_IDLE && (ARM || ARM64) && (ARCH_QCOM || COMPILE_TEST && !ARM64 && MMU
vim +/armada_drm_debugfs_init +111 drivers/gpu/drm/armada/armada_debugfs.c
107
108 int armada_drm_debugfs_init(struct drm_minor *minor)
109 {
110 if (!minor->debugfs_root)
> 111 return;
---
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: 35834 bytes --]
next prev parent reply other threads:[~2021-10-12 19:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 9:17 [PATCH 1/5] dri: cleanup debugfs error handling Nirmoy Das
2021-10-08 9:17 ` [PATCH 2/5] drm/i915: check dri root before debugfs init Nirmoy Das
2021-10-12 9:59 ` Wang, Zhi A
2021-10-12 10:19 ` Das, Nirmoy
2021-10-08 9:17 ` [PATCH 3/5] drm/radeon: " Nirmoy Das
2021-10-08 10:23 ` Christian König
2021-10-08 10:34 ` Das, Nirmoy
2021-10-08 9:17 ` [PATCH 4/5] drm/armada: check dri/crtc " Nirmoy Das
2021-10-12 19:40 ` kernel test robot [this message]
2021-10-08 9:17 ` [PATCH 5/5] drm/tegra: check root dentry " Nirmoy Das
2021-11-08 6:35 ` kernel test robot
2021-10-08 9:35 ` [PATCH 1/5] dri: cleanup debugfs error handling Thomas Zimmermann
2021-10-08 9:40 ` [Intel-gfx] " Jani Nikula
2021-10-08 11:07 ` Greg KH
2021-10-08 12:08 ` Das, Nirmoy
[not found] ` <02fc9da3-ebac-2df1-3a54-d764b273f91b@amd.com>
2021-10-08 12:56 ` Fw: " Das, Nirmoy
[not found] ` <c4f1464d-19b6-04a3-e2d8-a153bfbb050a@amd.com>
[not found] ` <YWBfvILqkBQ8VSYc@kroah.com>
2021-10-11 14:19 ` Christian König
2021-10-11 14:53 ` Greg KH
2021-10-11 16:38 ` Jani Nikula
2021-10-11 17:07 ` Greg KH
2021-10-11 18:43 ` Jani Nikula
2021-10-11 15:13 ` Das, Nirmoy
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=202110130358.vZd7yOQ1-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=nirmoy.das@amd.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