From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
mcanal@igalia.com, stanislaw.gruszka@linux.intel.com,
ogabbay@kernel.org, quic_jhugo@quicinc.com, daniel@ffwll.ch,
jani.nikula@linux.intel.com, mwen@igalia.com, maxime@cerno.tech,
wambui.karugax@gmail.com, dri-devel@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/5] drm/debugfs: rework debugfs directory creation v3
Date: Thu, 13 Apr 2023 23:39:10 +0800 [thread overview]
Message-ID: <202304132344.9oz5dfJI-lkp@intel.com> (raw)
In-Reply-To: <20230412145206.2483-3-christian.koenig@amd.com>
Hi Christian,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-intel/for-linux-next drm-intel/for-linux-next-fixes tegra/for-next linus/master v6.3-rc6 next-20230412]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Christian-K-nig/drm-debugfs-rework-debugfs-directory-creation-v3/20230412-235231
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230412145206.2483-3-christian.koenig%40amd.com
patch subject: [PATCH 2/5] drm/debugfs: rework debugfs directory creation v3
config: hexagon-randconfig-r002-20230409 (https://download.01.org/0day-ci/archive/20230413/202304132344.9oz5dfJI-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 9638da200e00bd069e6dd63604e14cbafede9324)
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/92a7a4f0fd59d427c5827c323692b76095f90efc
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Christian-K-nig/drm-debugfs-rework-debugfs-directory-creation-v3/20230412-235231
git checkout 92a7a4f0fd59d427c5827c323692b76095f90efc
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/gpu/drm/
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/202304132344.9oz5dfJI-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_drv.c:38:
In file included from include/drm/drm_accel.h:11:
In file included from include/drm/drm_file.h:39:
In file included from include/drm/drm_prime.h:37:
In file included from include/linux/scatterlist.h:9:
In file included from arch/hexagon/include/asm/io.h:334:
include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
val = __raw_readb(PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr));
~~~~~~~~~~ ^
include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu'
#define __le16_to_cpu(x) ((__force __u16)(__le16)(x))
^
In file included from drivers/gpu/drm/drm_drv.c:38:
In file included from include/drm/drm_accel.h:11:
In file included from include/drm/drm_file.h:39:
In file included from include/drm/drm_prime.h:37:
In file included from include/linux/scatterlist.h:9:
In file included from arch/hexagon/include/asm/io.h:334:
include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr));
~~~~~~~~~~ ^
include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu'
#define __le32_to_cpu(x) ((__force __u32)(__le32)(x))
^
In file included from drivers/gpu/drm/drm_drv.c:38:
In file included from include/drm/drm_accel.h:11:
In file included from include/drm/drm_file.h:39:
In file included from include/drm/drm_prime.h:37:
In file included from include/linux/scatterlist.h:9:
In file included from arch/hexagon/include/asm/io.h:334:
include/asm-generic/io.h:584:33: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
__raw_writeb(value, PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:594:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
__raw_writew((u16 __force)cpu_to_le16(value), PCI_IOBASE + addr);
~~~~~~~~~~ ^
include/asm-generic/io.h:604:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
__raw_writel((u32 __force)cpu_to_le32(value), PCI_IOBASE + addr);
~~~~~~~~~~ ^
>> drivers/gpu/drm/drm_drv.c:1011:2: error: call to undeclared function 'drm_debugfs_dev_fini'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drm_debugfs_dev_fini(dev);
^
drivers/gpu/drm/drm_drv.c:1011:2: note: did you mean 'drm_debugfs_dev_init'?
include/drm/drm_drv.h:596:13: note: 'drm_debugfs_dev_init' declared here
static void drm_debugfs_dev_init(struct drm_device *dev, struct dentry *root)
^
6 warnings and 1 error generated.
vim +/drm_debugfs_dev_fini +1011 drivers/gpu/drm/drm_drv.c
974
975 /**
976 * drm_dev_unregister - Unregister DRM device
977 * @dev: Device to unregister
978 *
979 * Unregister the DRM device from the system. This does the reverse of
980 * drm_dev_register() but does not deallocate the device. The caller must call
981 * drm_dev_put() to drop their final reference.
982 *
983 * A special form of unregistering for hotpluggable devices is drm_dev_unplug(),
984 * which can be called while there are still open users of @dev.
985 *
986 * This should be called first in the device teardown code to make sure
987 * userspace can't access the device instance any more.
988 */
989 void drm_dev_unregister(struct drm_device *dev)
990 {
991 if (drm_core_check_feature(dev, DRIVER_LEGACY))
992 drm_lastclose(dev);
993
994 dev->registered = false;
995
996 drm_client_dev_unregister(dev);
997
998 if (drm_core_check_feature(dev, DRIVER_MODESET))
999 drm_modeset_unregister_all(dev);
1000
1001 if (dev->driver->unload)
1002 dev->driver->unload(dev);
1003
1004 drm_legacy_pci_agp_destroy(dev);
1005 drm_legacy_rmmaps(dev);
1006
1007 remove_compat_control_link(dev);
1008 drm_minor_unregister(dev, DRM_MINOR_ACCEL);
1009 drm_minor_unregister(dev, DRM_MINOR_PRIMARY);
1010 drm_minor_unregister(dev, DRM_MINOR_RENDER);
> 1011 drm_debugfs_dev_fini(dev);
1012 }
1013 EXPORT_SYMBOL(drm_dev_unregister);
1014
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-13 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 14:52 DRM debugfs cleanup take 4 Christian König
2023-04-12 14:52 ` [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2 Christian König
2023-04-12 14:52 ` [PATCH 2/5] drm/debugfs: rework debugfs directory creation v3 Christian König
2023-04-13 11:29 ` kernel test robot
2023-04-13 15:39 ` kernel test robot [this message]
2023-04-16 16:03 ` Tomer Tayar
2023-04-17 7:18 ` Christian König
2023-04-17 10:26 ` Stanislaw Gruszka
2023-04-24 12:17 ` Christian König
2023-04-12 14:52 ` [PATCH 3/5] drm/debugfs: remove dev->debugfs_list and debugfs_mutex v2 Christian König
2023-04-12 15:11 ` Daniel Vetter
2023-04-13 9:34 ` Christian König
2023-04-13 13:45 ` Daniel Vetter
2023-04-12 14:52 ` [PATCH 4/5] drm/debugfs: rework drm_debugfs_create_files implementation Christian König
2023-04-12 14:52 ` [PATCH 5/5] drm/debugfs: remove debugfs_root pointer from minor Christian König
2023-06-01 15:59 ` DRM debugfs cleanup take 4 Oded Gabbay
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=202304132344.9oz5dfJI-lkp@intel.com \
--to=lkp@intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=llvm@lists.linux.dev \
--cc=maxime@cerno.tech \
--cc=mcanal@igalia.com \
--cc=mwen@igalia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=stanislaw.gruszka@linux.intel.com \
--cc=wambui.karugax@gmail.com \
/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.