From: kernel test robot <lkp@intel.com>
To: Philipp Zabel <p.zabel@pengutronix.de>, dri-devel@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, Thomas Zimmermann <tzimmermann@suse.de>,
kernel@pengutronix.de
Subject: Re: [PATCH 3/4] drm/plane: add drmm_universal_plane_alloc()
Date: Wed, 26 Aug 2020 23:26:07 +0800 [thread overview]
Message-ID: <202008262301.VuMgFMhI%lkp@intel.com> (raw)
In-Reply-To: <20200826123506.19560-3-p.zabel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
Hi Philipp,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on tegra-drm/drm/tegra/for-next drm-tip/drm-tip linus/master drm-exynos/exynos-drm-next v5.9-rc2 next-20200826]
[cannot apply to drm/drm-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/0day-ci/linux/commits/Philipp-Zabel/drm-add-drmm_encoder_alloc/20200826-203629
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-s001-20200826 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-191-g10164920-dirty
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/drm_plane.c:156:5: sparse: sparse: symbol '__drm_universal_plane_init' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 44545 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-08-26 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 12:35 [PATCH 1/4] drm: add drmm_encoder_alloc() Philipp Zabel
2020-08-26 12:35 ` [PATCH 2/4] drm/simple_kms_helper: add drmm_simple_encoder_alloc() Philipp Zabel
2020-08-26 12:35 ` [PATCH 3/4] drm/plane: add drmm_universal_plane_alloc() Philipp Zabel
2020-08-26 15:26 ` kernel test robot [this message]
2020-08-26 15:26 ` [RFC PATCH] drm/plane: __drm_universal_plane_init() can be static kernel test robot
2020-08-26 16:58 ` [PATCH 3/4] drm/plane: add drmm_universal_plane_alloc() kernel test robot
2020-08-26 19:47 ` kernel test robot
2020-08-31 9:37 ` Dan Carpenter
2020-08-26 12:35 ` [PATCH 4/4] drm/crtc: add drmm_crtc_alloc_with_planes() Philipp Zabel
2020-08-26 18:04 ` kernel test robot
2020-08-26 21:29 ` kernel test robot
2020-08-27 7:32 ` [drm/crtc] 236b7bc44a: BUG:stack_guard_page_was_hit_at(____ptrval____)(stack_is(____ptrval____)..(____ptrval____)) kernel test robot
2020-08-31 9:39 ` [PATCH 4/4] drm/crtc: add drmm_crtc_alloc_with_planes() Dan Carpenter
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=202008262301.VuMgFMhI%lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=kernel@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=tzimmermann@suse.de \
/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