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>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Jocelyn Falempe <jfalempe@redhat.com>
Subject: Re: [PATCH v4 3/7] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Wed, 16 Oct 2024 04:05:02 +0800 [thread overview]
Message-ID: <202410160342.rkkekxWK-lkp@intel.com> (raw)
In-Reply-To: <20241011105526.615812-4-jfalempe@redhat.com>
Hi Jocelyn,
kernel test robot noticed the following build errors:
[auto build test ERROR on 33c255312660653cf54f8019896b5dca28e3c580]
url: https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-client-squash-of-drm-client-pending-series/20241011-225715
base: 33c255312660653cf54f8019896b5dca28e3c580
patch link: https://lore.kernel.org/r/20241011105526.615812-4-jfalempe%40redhat.com
patch subject: [PATCH v4 3/7] drm/log: Introduce a new boot logger to draw the kmsg on the screen
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20241016/202410160342.rkkekxWK-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241016/202410160342.rkkekxWK-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/202410160342.rkkekxWK-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_log.c:347:6: error: redefinition of 'drm_log_register'
347 | void drm_log_register(struct drm_device *dev)
| ^~~~~~~~~~~~~~~~
In file included from drivers/gpu/drm/drm_log.c:21:
drivers/gpu/drm/drm_log.h:8:20: note: previous definition of 'drm_log_register' with type 'void(struct drm_device *)'
8 | static inline void drm_log_register(struct drm_device *dev) {}
| ^~~~~~~~~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=n] || GCC_PLUGINS [=y]) && MODULES [=y]
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [m]:
- RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
vim +/drm_log_register +347 drivers/gpu/drm/drm_log.c
342
343 /**
344 * drm_log_register() - Register a drm device to drm_log
345 * @dev: the drm device to register.
346 */
> 347 void drm_log_register(struct drm_device *dev)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-15 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 10:49 [PATCH v4 0/7] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-10-11 10:49 ` [PATCH v4 1/7] [NOT FOR REVIEW] drm/client, squash of drm client pending series Jocelyn Falempe
2024-10-11 10:49 ` [PATCH v4 2/7] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-10-11 10:50 ` [PATCH v4 3/7] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-10-15 20:05 ` kernel test robot [this message]
2024-10-11 10:50 ` [PATCH v4 4/7] drm/log: Do not draw if drm_master is taken Jocelyn Falempe
2024-10-11 10:50 ` [PATCH v4 5/7] drm/log: Color the timestamp, to improve readability Jocelyn Falempe
2024-10-11 10:50 ` [PATCH v4 6/7] drm/log: Implement suspend/resume Jocelyn Falempe
2024-10-11 10:50 ` [PATCH v4 7/7] drm/log: Add integer scaling support Jocelyn Falempe
2024-10-11 11:18 ` Jani Nikula
2024-10-11 11:58 ` 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=202410160342.rkkekxWK-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=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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