From: kernel test robot <lkp@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
daniel@ffwll.ch, airlied@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
javierm@redhat.com
Cc: linux-samsung-soc@vger.kernel.org,
Tomi Valkeinen <tomba@kernel.org>,
linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
oe-kbuild-all@lists.linux.dev, linux-tegra@vger.kernel.org,
freedreno@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Intel-gfx] [PATCH 07/11] drm/omapdrm: Use regular fbdev I/O helpers
Date: Sat, 13 May 2023 00:20:28 +0800 [thread overview]
Message-ID: <202305130058.VuW3nBPS-lkp@intel.com> (raw)
In-Reply-To: <20230512084152.31233-8-tzimmermann@suse.de>
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on 451e49cfbaa90720149e63f4fa9c7824013c783d]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/drm-armada-Use-regular-fbdev-I-O-helpers/20230512-164432
base: 451e49cfbaa90720149e63f4fa9c7824013c783d
patch link: https://lore.kernel.org/r/20230512084152.31233-8-tzimmermann%40suse.de
patch subject: [Intel-gfx] [PATCH 07/11] drm/omapdrm: Use regular fbdev I/O helpers
config: arm-allmodconfig (https://download.01.org/0day-ci/archive/20230513/202305130058.VuW3nBPS-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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/f9113ec6815b748d0b917f78527582b8b08deb40
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Thomas-Zimmermann/drm-armada-Use-regular-fbdev-I-O-helpers/20230512-164432
git checkout f9113ec6815b748d0b917f78527582b8b08deb40
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/gpu/drm/omapdrm/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202305130058.VuW3nBPS-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/omapdrm/omap_fbdev.c:306:6: error: redefinition of 'omap_fbdev_setup'
306 | void omap_fbdev_setup(struct drm_device *dev)
| ^~~~~~~~~~~~~~~~
In file included from drivers/gpu/drm/omapdrm/omap_fbdev.c:19:
drivers/gpu/drm/omapdrm/omap_fbdev.h:17:20: note: previous definition of 'omap_fbdev_setup' with type 'void(struct drm_device *)'
17 | static inline void omap_fbdev_setup(struct drm_device *dev)
| ^~~~~~~~~~~~~~~~
vim +/omap_fbdev_setup +306 drivers/gpu/drm/omapdrm/omap_fbdev.c
9e69bcd88e4593 Thomas Zimmermann 2023-04-03 305
9e69bcd88e4593 Thomas Zimmermann 2023-04-03 @306 void omap_fbdev_setup(struct drm_device *dev)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-05-12 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 8:41 [Intel-gfx] [PATCH 00/11] drm/fbdev: Remove DRM's helpers for fbdev I/O Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 01/11] drm/armada: Use regular fbdev I/O helpers Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 02/11] drm/exynos: " Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 03/11] drm/gma500: " Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 04/11] drm/radeon: " Thomas Zimmermann
2023-05-12 13:55 ` Deucher, Alexander
2023-05-12 8:41 ` [Intel-gfx] [PATCH 05/11] drm/fbdev-dma: " Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 06/11] drm/msm: " Thomas Zimmermann
2023-05-12 9:45 ` Dmitry Baryshkov
2023-05-12 8:41 ` [Intel-gfx] [PATCH 07/11] drm/omapdrm: " Thomas Zimmermann
2023-05-12 16:20 ` kernel test robot [this message]
2023-05-12 8:41 ` [Intel-gfx] [PATCH 08/11] drm/tegra: " Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 09/11] drm/fb-helper: Export helpers for marking damage areas Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 10/11] drm/fbdev-generic: Implement dedicated fbdev I/O helpers Thomas Zimmermann
2023-05-12 8:41 ` [Intel-gfx] [PATCH 11/11] drm/i915: " Thomas Zimmermann
2023-05-12 9:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/fbdev: Remove DRM's helpers for fbdev I/O Patchwork
2023-05-12 9:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-05-12 10:29 ` [Intel-gfx] [PATCH 00/11] " Sam Ravnborg
2023-05-12 11:49 ` Thomas Zimmermann
2023-05-12 13:41 ` Sam Ravnborg
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=202305130058.VuW3nBPS-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tomba@kernel.org \
--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