Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, intel-xe@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Matthew Brost <matthew.brost@intel.com>
Subject: [drm-xe:drm-xe-next 1/4] drivers/gpu/drm/xe/xe_bo.c:1635:9: error: implicit declaration of function 'drmm_release_action'; did you mean 'devm_release_action'?
Date: Tue, 6 Feb 2024 06:30:10 +0800	[thread overview]
Message-ID: <202402060635.9vgI8A76-lkp@intel.com> (raw)

tree:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head:   897c5b367db8affee69823c7e639caf33187bdf2
commit: 30b71bce350e4ab5e495697838b1fb8478970140 [1/4] drm/xe/guc: Allocate GuC data structures in system memory for initial load
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20240206/202402060635.9vgI8A76-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240206/202402060635.9vgI8A76-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/202402060635.9vgI8A76-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpu/drm/xe/xe_bo.c: In function 'xe_managed_bo_reinit_in_vram':
>> drivers/gpu/drm/xe/xe_bo.c:1635:9: error: implicit declaration of function 'drmm_release_action'; did you mean 'devm_release_action'? [-Werror=implicit-function-declaration]
    1635 |         drmm_release_action(&xe->drm, __xe_bo_unpin_map_no_vm, *src);
         |         ^~~~~~~~~~~~~~~~~~~
         |         devm_release_action
   cc1: some warnings being treated as errors


vim +1635 drivers/gpu/drm/xe/xe_bo.c

  1608	
  1609	/**
  1610	 * xe_managed_bo_reinit_in_vram
  1611	 * @xe: xe device
  1612	 * @tile: Tile where the new buffer will be created
  1613	 * @src: Managed buffer object allocated in system memory
  1614	 *
  1615	 * Replace a managed src buffer object allocated in system memory with a new
  1616	 * one allocated in vram, copying the data between them.
  1617	 * Buffer object in VRAM is not going to have the same GGTT address, the caller
  1618	 * is responsible for making sure that any old references to it are updated.
  1619	 *
  1620	 * Returns 0 for success, negative error code otherwise.
  1621	 */
  1622	int xe_managed_bo_reinit_in_vram(struct xe_device *xe, struct xe_tile *tile, struct xe_bo **src)
  1623	{
  1624		struct xe_bo *bo;
  1625	
  1626		xe_assert(xe, IS_DGFX(xe));
  1627		xe_assert(xe, !(*src)->vmap.is_iomem);
  1628	
  1629		bo = xe_managed_bo_create_from_data(xe, tile, (*src)->vmap.vaddr, (*src)->size,
  1630						    XE_BO_CREATE_VRAM_IF_DGFX(tile) |
  1631						    XE_BO_CREATE_GGTT_BIT);
  1632		if (IS_ERR(bo))
  1633			return PTR_ERR(bo);
  1634	
> 1635		drmm_release_action(&xe->drm, __xe_bo_unpin_map_no_vm, *src);
  1636		*src = bo;
  1637	
  1638		return 0;
  1639	}
  1640	

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

                 reply	other threads:[~2024-02-05 22:30 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=202402060635.9vgI8A76-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rodrigo.vivi@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