From: kernel test robot <lkp@intel.com>
To: Sui Jingfeng <15330273260@189.cn>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Roland Scheidegger <sroland@vmware.com>,
Zack Rusin <zackr@vmware.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Dan Carpenter <error27@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
Sam Ravnborg <sam@ravnborg.org>,
"David S . Miller" <davem@davemloft.net>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Lucas Stach <l.stach@pengutronix.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Ilia Mirkin <imirkin@alum.mit.edu>,
Qing Zhang <zhangqing@loongson.cn>,
suijingfeng <suijingfeng@loongson.cn>
Cc: kbuild-all@lists.01.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 5/6] drm/loongson: add drm driver for loongson display controller
Date: Sun, 27 Mar 2022 21:52:32 +0800 [thread overview]
Message-ID: <202203272117.q6tMwBFo-lkp@intel.com> (raw)
In-Reply-To: <20220327113846.2498146-6-15330273260@189.cn>
Hi Sui,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on robh/for-next linus/master v5.17 next-20220325]
[cannot apply to mripard/sunxi/for-next]
[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/intel-lab-lkp/linux/commits/Sui-Jingfeng/drm-loongson-add-drm-driver-for-loongson-display-controller/20220327-194016
base: git://anongit.freedesktop.org/drm/drm drm-next
config: parisc-randconfig-r003-20220327 (https://download.01.org/0day-ci/archive/20220327/202203272117.q6tMwBFo-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.2.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/intel-lab-lkp/linux/commit/e90d831d05f2c1b5631fd706fb449e83e64f632c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Sui-Jingfeng/drm-loongson-add-drm-driver-for-loongson-display-controller/20220327-194016
git checkout e90d831d05f2c1b5631fd706fb449e83e64f632c
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc SHELL=/bin/bash drivers/gpu/drm/loongson/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/loongson/lsdc_debugfs.c:149: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* vram debugfs related ...
vim +149 drivers/gpu/drm/loongson/lsdc_debugfs.c
147
148 /**
> 149 * vram debugfs related ...
150 */
151 static int lsdc_vram_mm_show(struct seq_file *m, void *data)
152 {
153 struct drm_info_node *node = (struct drm_info_node *)m->private;
154 struct drm_vram_mm *vmm = node->minor->dev->vram_mm;
155 struct ttm_resource_manager *man = ttm_manager_type(&vmm->bdev, TTM_PL_VRAM);
156 struct drm_printer p = drm_seq_file_printer(m);
157
158 ttm_resource_manager_debug(man, &p);
159 return 0;
160 }
161
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-03-27 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 11:38 [PATCH v12 0/6] drm/loongson: add drm driver for loongson display controller Sui Jingfeng
2022-03-27 11:38 ` [PATCH v12 1/6] MIPS: Loongson64: dts: update the display controller device node Sui Jingfeng
2022-03-27 11:38 ` [PATCH v12 2/6] MIPS: Loongson64: introduce board specific dts and add model property Sui Jingfeng
2022-03-27 11:38 ` [PATCH v12 3/6] dt-bindings: display: Add Loongson display controller Sui Jingfeng
2022-03-27 12:54 ` Jiaxun Yang
2022-03-28 1:52 ` Sui Jingfeng
2022-03-27 14:02 ` Rob Herring
2022-03-28 2:24 ` Sui Jingfeng
2022-03-27 11:38 ` [PATCH v12 4/6] MIPS: Loongson64: defconfig: enable display bridge drivers Sui Jingfeng
2022-03-27 11:38 ` [PATCH v12 5/6] drm/loongson: add drm driver for loongson display controller Sui Jingfeng
2022-03-27 13:52 ` kernel test robot [this message]
2022-03-27 11:38 ` [PATCH v12 6/6] MAINTAINERS: add maintainers for DRM LSDC driver Sui Jingfeng
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=202203272117.q6tMwBFo-lkp@intel.com \
--to=lkp@intel.com \
--cc=15330273260@189.cn \
--cc=airlied@linux.ie \
--cc=andrey.zhizhikin@leica-geosystems.com \
--cc=christian.gmeiner@gmail.com \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=error27@gmail.com \
--cc=imirkin@alum.mit.edu \
--cc=jiaxun.yang@flygoat.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sroland@vmware.com \
--cc=suijingfeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.com \
--cc=zhangqing@loongson.cn \
/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).