Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/4] drm/ttm: Use LRU hitches
Date: Sat, 17 Feb 2024 11:42:00 +0800	[thread overview]
Message-ID: <202402171115.ELbaBdCa-lkp@intel.com> (raw)
In-Reply-To: <20240216131446.101961-3-thomas.hellstrom@linux.intel.com>

Hi Thomas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.8-rc4 next-20240216]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Thomas-Hellstr-m/drm-ttm-Allow-TTM-LRU-list-nodes-of-different-types/20240216-211801
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:    https://lore.kernel.org/r/20240216131446.101961-3-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH 2/4] drm/ttm: Use LRU hitches
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240217/202402171115.ELbaBdCa-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240217/202402171115.ELbaBdCa-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/202402171115.ELbaBdCa-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/ttm/ttm_resource.c:58: warning: expecting prototype for ttm_resource_cursor_fini_locked(). Prototype was for ttm_resource_cursor_fini() instead


vim +58 drivers/gpu/drm/ttm/ttm_resource.c

    48	
    49	/**
    50	 * ttm_resource_cursor_fini_locked() - Finalize the LRU list cursor usage
    51	 * @cursor: The struct ttm_resource_cursor to finalize.
    52	 *
    53	 * The function pulls the LRU list cursor off any lists it was previusly
    54	 * attached to. Needs to be called without the LRU list lock held. The
    55	 * function can be called multiple times after eachother.
    56	 */
    57	void ttm_resource_cursor_fini(struct ttm_resource_cursor *cursor)
  > 58	{
    59		spinlock_t *lru_lock = &cursor->man->bdev->lru_lock;
    60	
    61		spin_lock(lru_lock);
    62		ttm_resource_cursor_fini_locked(cursor);
    63		spin_unlock(lru_lock);
    64	}
    65	

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

  reply	other threads:[~2024-02-17  3:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 13:14 [PATCH 0/4] TTM unlockable restartable LRU list iteration Thomas Hellström
2024-02-16 13:14 ` [PATCH 1/4] drm/ttm: Allow TTM LRU list nodes of different types Thomas Hellström
2024-02-16 13:14 ` [PATCH 2/4] drm/ttm: Use LRU hitches Thomas Hellström
2024-02-17  3:42   ` kernel test robot [this message]
2024-02-16 13:14 ` [PATCH 3/4] drm/ttm: Consider hitch moves within bulk sublist moves Thomas Hellström
2024-02-17  0:02   ` kernel test robot
2024-02-17 16:45   ` kernel test robot
2024-02-16 13:14 ` [PATCH 4/4] drm/ttm: Allow continued swapout after -ENOSPC falure Thomas Hellström
2024-02-16 21:40 ` ✗ Fi.CI.CHECKPATCH: warning for TTM unlockable restartable LRU list iteration Patchwork
2024-02-16 21:40 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-02-16 21:56 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-17 14:03 ` ✗ Fi.CI.IGT: failure " Patchwork

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=202402171115.ELbaBdCa-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=thomas.hellstrom@linux.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