From: kernel test robot <lkp@intel.com>
To: Tomohito Esaki <etom@igel.co.jp>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [drm-misc:drm-misc-next 3/4] drivers/gpu/drm/sprd/sprd_drm.c:46:25: error: 'struct drm_mode_config' has no member named 'allow_fb_modifiers'
Date: Tue, 1 Feb 2022 09:54:31 +0800 [thread overview]
Message-ID: <202202010923.1fCku8oB-lkp@intel.com> (raw)
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: d80976d9ffd9d7f89a26134a299b236910477f3b
commit: 3d082157a24216ca084082ce421a37d14ecfcfad [3/4] drm: remove allow_fb_modifiers
config: arc-randconfig-r043-20220130 (https://download.01.org/0day-ci/archive/20220201/202202010923.1fCku8oB-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 11.2.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
git remote add drm-misc git://anongit.freedesktop.org/drm/drm-misc
git fetch --no-tags drm-misc drm-misc-next
git checkout 3d082157a24216ca084082ce421a37d14ecfcfad
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash drivers/gpu/drm/sprd/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/sprd/sprd_drm.c: In function 'sprd_drm_mode_config_init':
>> drivers/gpu/drm/sprd/sprd_drm.c:46:25: error: 'struct drm_mode_config' has no member named 'allow_fb_modifiers'
46 | drm->mode_config.allow_fb_modifiers = true;
| ^
vim +46 drivers/gpu/drm/sprd/sprd_drm.c
43531edd53f07c Kevin Tang 2021-12-07 39
43531edd53f07c Kevin Tang 2021-12-07 40 static void sprd_drm_mode_config_init(struct drm_device *drm)
43531edd53f07c Kevin Tang 2021-12-07 41 {
43531edd53f07c Kevin Tang 2021-12-07 42 drm->mode_config.min_width = 0;
43531edd53f07c Kevin Tang 2021-12-07 43 drm->mode_config.min_height = 0;
43531edd53f07c Kevin Tang 2021-12-07 44 drm->mode_config.max_width = 8192;
43531edd53f07c Kevin Tang 2021-12-07 45 drm->mode_config.max_height = 8192;
43531edd53f07c Kevin Tang 2021-12-07 @46 drm->mode_config.allow_fb_modifiers = true;
43531edd53f07c Kevin Tang 2021-12-07 47
43531edd53f07c Kevin Tang 2021-12-07 48 drm->mode_config.funcs = &sprd_drm_mode_config_funcs;
43531edd53f07c Kevin Tang 2021-12-07 49 drm->mode_config.helper_private = &sprd_drm_mode_config_helper;
43531edd53f07c Kevin Tang 2021-12-07 50 }
43531edd53f07c Kevin Tang 2021-12-07 51
:::::: The code at line 46 was first introduced by commit
:::::: 43531edd53f07cbe977a0b33dea6dd6c29b21fea drm/sprd: add Unisoc's drm kms master
:::::: TO: Kevin Tang <kevin3.tang@gmail.com>
:::::: CC: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-01 1:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202202010923.1fCku8oB-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=etom@igel.co.jp \
--cc=kbuild-all@lists.01.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
/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®