All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mripard:drm/reset-state-flag 122/152] drivers/gpu/drm/vmwgfx/vmwgfx_kms.c:365:1: error: static declaration of 'vmw_du_connector_create_state' follows non-static declaration
Date: Fri, 11 Sep 2026 13:30:56 +0800	[thread overview]
Message-ID: <202609111334.nb0aii5K-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git drm/reset-state-flag
head:   3d18732b927902aaa841e0ebb77f3feaf8e519a9
commit: 3eb17b4de4dd70e92ea0fca2fdf4b2a12379312e [122/152] drm/vmwgfx: Convert to atomic_create_state
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260911/202609111334.nb0aii5K-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 96295a1412f9afbee9d4a3c2701e83f5a529a9cc)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260911/202609111334.nb0aii5K-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/202609111334.nb0aii5K-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/vmwgfx/vmwgfx_kms.c:365:1: error: static declaration of 'vmw_du_connector_create_state' follows non-static declaration
     365 | vmw_du_connector_create_state(struct drm_connector *connector)
         | ^
   drivers/gpu/drm/vmwgfx/vmwgfx_kms.h:429:1: note: previous declaration is here
     429 | vmw_du_connector_create_state(struct drm_connector *connector);
         | ^
   1 error generated.


vim +/vmw_du_connector_create_state +365 drivers/gpu/drm/vmwgfx/vmwgfx_kms.c

   356	
   357	
   358	/**
   359	 * vmw_du_connector_create_state - creates a blank vmw connector state
   360	 * @connector: DRM connector
   361	 *
   362	 * Allocates a new empty state object for @connector.
   363	 */
   364	static struct drm_connector_state *
 > 365	vmw_du_connector_create_state(struct drm_connector *connector)
   366	{
   367		struct vmw_connector_state *vcs;
   368	
   369		vcs = kzalloc_obj(*vcs);
   370		if (!vcs) {
   371			DRM_ERROR("Cannot allocate vmw_connector_state\n");
   372			return ERR_PTR(-ENOMEM);
   373		}
   374	
   375		__drm_atomic_helper_connector_state_init(&vcs->base, connector);
   376	
   377		return &vcs->base;
   378	}
   379	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-09-11  5:32 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=202609111334.nb0aii5K-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mripard@kernel.org \
    --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 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.