All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-lts 152/152] drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c:157: warning: Function parameter or struct member 'flags' not described in 'amdgpu_sync_fence'
Date: Tue, 17 Nov 2026 01:46:04 +0100	[thread overview]
Message-ID: <202611170116.ffmj2zKA-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android16-6.12-lts
head:   c5e3d3a3d3b60eb95c36e3c49dbfe7a34c220c5a
commit: 7770f84cf3c19f5f26c90db3466f532f0fed8364 [152/152] drm/amdgpu: use GFP_NOWAIT for memory allocations
config: x86_64-randconfig-r2307-20261116 (https://download.01.org/0day-ci/archive/20261117/202611170116.ffmj2zKA-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261117/202611170116.ffmj2zKA-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/202611170116.ffmj2zKA-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c:157: warning: Function parameter or struct member 'flags' not described in 'amdgpu_sync_fence'


vim +157 drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c

832a902f9433b81 Christian König 2016-02-15  146  
d38ceaf99ed015f Alex Deucher    2015-04-20  147  /**
91e1a5207edec9e Christian König 2015-07-06  148   * amdgpu_sync_fence - remember to sync to this fence
d38ceaf99ed015f Alex Deucher    2015-04-20  149   *
d38ceaf99ed015f Alex Deucher    2015-04-20  150   * @sync: sync object to add fence to
e095fc17bbd216c Christian König 2019-11-29  151   * @f: fence to sync to
d38ceaf99ed015f Alex Deucher    2015-04-20  152   *
e095fc17bbd216c Christian König 2019-11-29  153   * Add the fence to the sync object.
d38ceaf99ed015f Alex Deucher    2015-04-20  154   */
7770f84cf3c19f5 Christian König 2026-09-22  155  int amdgpu_sync_fence(struct amdgpu_sync *sync, struct dma_fence *f,
7770f84cf3c19f5 Christian König 2026-09-22  156  		      gfp_t flags)
d38ceaf99ed015f Alex Deucher    2015-04-20 @157  {
f91b3a694181209 Christian König 2015-08-20  158  	struct amdgpu_sync_entry *e;
d38ceaf99ed015f Alex Deucher    2015-04-20  159  
91e1a5207edec9e Christian König 2015-07-06  160  	if (!f)
91e1a5207edec9e Christian König 2015-07-06  161  		return 0;
3c62338c26bf267 Chunming Zhou   2015-08-20  162  
174b328bc89b5fa Christian König 2020-05-27  163  	if (amdgpu_sync_add_later(sync, f))
f91b3a694181209 Christian König 2015-08-20  164  		return 0;
f91b3a694181209 Christian König 2015-08-20  165  
7770f84cf3c19f5 Christian König 2026-09-22  166  	e = kmem_cache_alloc(amdgpu_sync_slab, flags);
f91b3a694181209 Christian König 2015-08-20  167  	if (!e)
f91b3a694181209 Christian König 2015-08-20  168  		return -ENOMEM;
f91b3a694181209 Christian König 2015-08-20  169  
f91b3a694181209 Christian König 2015-08-20  170  	hash_add(sync->fences, &e->node, f->context);
f54d1867005c332 Chris Wilson    2016-10-25  171  	e->fence = dma_fence_get(f);
f91b3a694181209 Christian König 2015-08-20  172  	return 0;
f91b3a694181209 Christian König 2015-08-20  173  }
d38ceaf99ed015f Alex Deucher    2015-04-20  174  

:::::: The code at line 157 was first introduced by commit
:::::: d38ceaf99ed015f2a0b9af3499791bd3a3daae21 drm/amdgpu: add core driver (v4)

:::::: TO: Alex Deucher <alexander.deucher@amd.com>
:::::: CC: Alex Deucher <alexander.deucher@amd.com>

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

                 reply	other threads:[~2026-11-17  0:47 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=202611170116.ffmj2zKA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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.