From: kernel test robot <lkp@intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
John Ogness <john.ogness@linutronix.de>,
Javier Martinez Canillas <javierm@redhat.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
bluescreen_avenger@verizon.net,
Caleb Connolly <caleb.connolly@linaro.org>,
Petr Mladek <pmladek@suse.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jocelyn Falempe <jfalempe@redhat.com>
Subject: Re: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Wed, 6 Nov 2024 09:30:45 +0800 [thread overview]
Message-ID: <202411060951.mK9Fi0fi-lkp@intel.com> (raw)
In-Reply-To: <20241105125109.226866-3-jfalempe@redhat.com>
Hi Jocelyn,
kernel test robot noticed the following build errors:
[auto build test ERROR on d78f0ee0406803cda8801fd5201746ccf89e5e4a]
url: https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-panic-Move-drawing-functions-to-drm_draw/20241105-205432
base: d78f0ee0406803cda8801fd5201746ccf89e5e4a
patch link: https://lore.kernel.org/r/20241105125109.226866-3-jfalempe%40redhat.com
patch subject: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen
config: hexagon-randconfig-002-20241106 (https://download.01.org/0day-ci/archive/20241106/202411060951.mK9Fi0fi-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411060951.mK9Fi0fi-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411060951.mK9Fi0fi-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: drm_client_setup
>>> referenced by komeda_drv.c:87 (drivers/gpu/drm/arm/display/komeda/komeda_drv.c:87)
>>> drivers/gpu/drm/arm/display/komeda/komeda_drv.o:(komeda_platform_probe) in archive vmlinux.a
>>> referenced by komeda_drv.c:87 (drivers/gpu/drm/arm/display/komeda/komeda_drv.c:87)
>>> drivers/gpu/drm/arm/display/komeda/komeda_drv.o:(komeda_platform_probe) in archive vmlinux.a
>>> referenced by vkms_drv.c:230 (drivers/gpu/drm/vkms/vkms_drv.c:230)
>>> drivers/gpu/drm/vkms/vkms_drv.o:(vkms_init) in archive vmlinux.a
>>> referenced 23 more times
--
>> ld.lld: error: undefined symbol: drm_client_setup_with_fourcc
>>> referenced by arcpgu.c:399 (drivers/gpu/drm/tiny/arcpgu.c:399)
>>> drivers/gpu/drm/tiny/arcpgu.o:(arcpgu_probe) in archive vmlinux.a
>>> referenced by arcpgu.c:399 (drivers/gpu/drm/tiny/arcpgu.c:399)
>>> drivers/gpu/drm/tiny/arcpgu.o:(arcpgu_probe) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-06 1:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 12:42 [PATCH v6 0/6] " Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 1/6] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-11-05 13:16 ` John Ogness
2024-11-06 0:38 ` kernel test robot
2024-11-06 1:30 ` kernel test robot [this message]
2024-11-05 12:42 ` [PATCH v6 3/6] drm/log: Do not draw if drm_master is taken Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 4/6] drm/log: Color the timestamp, to improve readability Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 5/6] drm/log: Implement suspend/resume Jocelyn Falempe
2024-11-05 13:17 ` John Ogness
2024-11-05 15:08 ` Petr Mladek
2024-11-05 12:42 ` [PATCH v6 6/6] drm/log: Add integer scaling support Jocelyn Falempe
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=202411060951.mK9Fi0fi-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=bluescreen_avenger@verizon.net \
--cc=caleb.connolly@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gpiccoli@igalia.com \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmladek@suse.com \
--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
all inboxes | Powered by JetHome®