From: kernel test robot <lkp@intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
dri-devel@lists.freedesktop.org,
Javier Martinez Canillas <javierm@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [drm-misc:drm-misc-next 4/4] drivers/gpu/drm/drm_panic.c:712:6: error: no previous prototype for function 'drm_panic_is_enabled'
Date: Sun, 21 Jul 2024 02:56:29 +0800 [thread overview]
Message-ID: <202407210209.qmItlGt0-lkp@intel.com> (raw)
Hi Jocelyn,
First bad commit (maybe != root cause):
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: 7e33fc2ff6754b5ff39b11297f713cd0841d9962
commit: 3a9b77cee7502f7450c725d4ead2c4a44924d158 [4/4] drm/panic: Remove build time dependency with FRAMEBUFFER_CONSOLE
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240721/202407210209.qmItlGt0-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240721/202407210209.qmItlGt0-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/202407210209.qmItlGt0-lkp@intel.com/
Note: the drm-misc/drm-misc-next HEAD 7e33fc2ff6754b5ff39b11297f713cd0841d9962 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_panic.c:712:6: error: no previous prototype for function 'drm_panic_is_enabled' [-Werror,-Wmissing-prototypes]
712 | bool drm_panic_is_enabled(struct drm_device *dev)
| ^
drivers/gpu/drm/drm_panic.c:712:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
712 | bool drm_panic_is_enabled(struct drm_device *dev)
| ^
| static
1 error generated.
vim +/drm_panic_is_enabled +712 drivers/gpu/drm/drm_panic.c
813ca3aa8fecac Jocelyn Falempe 2024-04-09 705
9f774c42a908af Jocelyn Falempe 2024-07-17 706 /**
9f774c42a908af Jocelyn Falempe 2024-07-17 707 * drm_panic_is_enabled
9f774c42a908af Jocelyn Falempe 2024-07-17 708 * @dev: the drm device that may supports drm_panic
9f774c42a908af Jocelyn Falempe 2024-07-17 709 *
9f774c42a908af Jocelyn Falempe 2024-07-17 710 * returns true if the drm device supports drm_panic
9f774c42a908af Jocelyn Falempe 2024-07-17 711 */
9f774c42a908af Jocelyn Falempe 2024-07-17 @712 bool drm_panic_is_enabled(struct drm_device *dev)
9f774c42a908af Jocelyn Falempe 2024-07-17 713 {
9f774c42a908af Jocelyn Falempe 2024-07-17 714 struct drm_plane *plane;
9f774c42a908af Jocelyn Falempe 2024-07-17 715
9f774c42a908af Jocelyn Falempe 2024-07-17 716 if (!dev->mode_config.num_total_plane)
9f774c42a908af Jocelyn Falempe 2024-07-17 717 return false;
9f774c42a908af Jocelyn Falempe 2024-07-17 718
9f774c42a908af Jocelyn Falempe 2024-07-17 719 drm_for_each_plane(plane, dev)
9f774c42a908af Jocelyn Falempe 2024-07-17 720 if (plane->helper_private && plane->helper_private->get_scanout_buffer)
9f774c42a908af Jocelyn Falempe 2024-07-17 721 return true;
9f774c42a908af Jocelyn Falempe 2024-07-17 722 return false;
9f774c42a908af Jocelyn Falempe 2024-07-17 723 }
9f774c42a908af Jocelyn Falempe 2024-07-17 724 EXPORT_SYMBOL(drm_panic_is_enabled);
9f774c42a908af Jocelyn Falempe 2024-07-17 725
:::::: The code at line 712 was first introduced by commit
:::::: 9f774c42a908affba615bbed7463dd4f904dd5f1 drm/panic: Add drm_panic_is_enabled()
:::::: TO: Jocelyn Falempe <jfalempe@redhat.com>
:::::: CC: Jocelyn Falempe <jfalempe@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-20 18:56 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=202407210209.qmItlGt0-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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