linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andi Shyti <andi.shyti@linux.intel.com>
Subject: [linux-next:master 5707/10546] drivers/gpu/drm/i915/i915_driver.c:1806:24: error: 'i915_drm_client_fdinfo' undeclared here (not in a function); did you mean 'i915_drm_client_alloc'?
Date: Sun, 18 Jun 2023 00:04:53 +0800	[thread overview]
Message-ID: <202306180044.rvrE6n8B-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   f7efed9f38f886edb450041b82a6f15d663c98f8
commit: e894b724c316d9b45d963f929c97578cdffbbe8d [5707/10546] drm/i915: Use the fdinfo helper
config: i386-buildonly-randconfig-r004-20230617 (https://download.01.org/0day-ci/archive/20230618/202306180044.rvrE6n8B-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230618/202306180044.rvrE6n8B-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/202306180044.rvrE6n8B-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/i915/i915_driver.c:1806:24: error: 'i915_drm_client_fdinfo' undeclared here (not in a function); did you mean 'i915_drm_client_alloc'?
    1806 |         .show_fdinfo = i915_drm_client_fdinfo,
         |                        ^~~~~~~~~~~~~~~~~~~~~~
         |                        i915_drm_client_alloc


vim +1806 drivers/gpu/drm/i915/i915_driver.c

  1793	
  1794	static const struct drm_driver i915_drm_driver = {
  1795		/* Don't use MTRRs here; the Xserver or userspace app should
  1796		 * deal with them for Intel hardware.
  1797		 */
  1798		.driver_features =
  1799		    DRIVER_GEM |
  1800		    DRIVER_RENDER | DRIVER_MODESET | DRIVER_ATOMIC | DRIVER_SYNCOBJ |
  1801		    DRIVER_SYNCOBJ_TIMELINE,
  1802		.release = i915_driver_release,
  1803		.open = i915_driver_open,
  1804		.lastclose = i915_driver_lastclose,
  1805		.postclose = i915_driver_postclose,
> 1806		.show_fdinfo = i915_drm_client_fdinfo,

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


                 reply	other threads:[~2023-06-17 16:05 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=202306180044.rvrE6n8B-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tvrtko.ursulin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox