From: kernel test robot <lkp@intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Sun, 4 Aug 2024 01:49:40 +0800 [thread overview]
Message-ID: <202408040107.P9hJ7MiY-lkp@intel.com> (raw)
In-Reply-To: <20240801100640.462606-4-jfalempe@redhat.com>
Hi Jocelyn,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on bb99c51bdaa846bddb85a1e7acca3a3aa5e9f082]
url: https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-panic-Squash-of-pending-series/20240802-204640
base: bb99c51bdaa846bddb85a1e7acca3a3aa5e9f082
patch link: https://lore.kernel.org/r/20240801100640.462606-4-jfalempe%40redhat.com
patch subject: [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen
config: i386-buildonly-randconfig-006-20240803 (https://download.01.org/0day-ci/archive/20240804/202408040107.P9hJ7MiY-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240804/202408040107.P9hJ7MiY-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/202408040107.P9hJ7MiY-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: drm_log_register
>>> referenced by drm_drv.c
>>> drivers/gpu/drm/drm_drv.o:(drm_dev_register) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-03 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 10:04 [RFC PATCH 0/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-08-01 10:04 ` [RFC PATCH 1/3] [NOT FOR REVIEW] drm/panic: Squash of pending series Jocelyn Falempe
2024-08-01 10:04 ` [RFC PATCH 2/3] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-08-01 10:04 ` [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-08-01 10:51 ` John Ogness
2024-08-01 13:52 ` Jocelyn Falempe
2024-08-01 14:28 ` John Ogness
2024-09-05 15:22 ` John Ogness
2024-09-06 7:53 ` Jocelyn Falempe
2024-09-06 8:27 ` John Ogness
2024-09-06 8:47 ` John Ogness
2024-09-06 16:29 ` Jocelyn Falempe
2024-08-03 17:49 ` kernel test robot [this message]
2024-08-03 17:49 ` kernel test robot
2024-08-01 10:36 ` [RFC PATCH 0/3] " John Ogness
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=202408040107.P9hJ7MiY-lkp@intel.com \
--to=lkp@intel.com \
--cc=jfalempe@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.