From: kernel test robot <lkp@intel.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: [kbingham-rcar:kbingham/drm-misc/next/sn65dsi86/hpd 11/15] ERROR: modpost: "drm_atomic_helper_bridge_dsi_input_bus_fmt" [drivers/gpu/drm/bridge/parade-ps8640.ko] undefined!
Date: Mon, 21 Mar 2022 10:31:58 +0800 [thread overview]
Message-ID: <202203211043.tkkRnByV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git kbingham/drm-misc/next/sn65dsi86/hpd
head: b55ca0e75f467b5c011ef8bfbcff0a2234cf9695
commit: e10c501b6016d478e18c24982e9afb0fa978e896 [11/15] drm/bridge: ps8640: plug atomic_get_input_bus_fmts
config: x86_64-randconfig-c022-20220321 (https://download.01.org/0day-ci/archive/20220321/202203211043.tkkRnByV-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git/commit/?id=e10c501b6016d478e18c24982e9afb0fa978e896
git remote add kbingham-rcar https://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git
git fetch --no-tags kbingham-rcar kbingham/drm-misc/next/sn65dsi86/hpd
git checkout e10c501b6016d478e18c24982e9afb0fa978e896
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
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 >>, old ones prefixed by <<):
>> ERROR: modpost: "drm_atomic_helper_bridge_dsi_input_bus_fmt" [drivers/gpu/drm/bridge/parade-ps8640.ko] undefined!
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-03-21 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 2:31 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-11 8:46 kernel test robot
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=202203211043.tkkRnByV-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®