From: kernel test robot <lkp@intel.com>
To: Donald Robson <donald.robson@imgtec.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Maxime Ripard <mripard@kernel.org>,
Matt Coster <matt.coster@imgtec.com>,
Sarah Walker <sarah.walker@imgtec.com>
Subject: [linux-next:master 1963/7726] drivers/gpu/drm/imagination/pvr_mmu.c:170: warning: Excess struct member 'pvr_dev' description in 'pvr_mmu_backing_page'
Date: Fri, 15 Dec 2023 00:18:55 +0800 [thread overview]
Message-ID: <202312150042.9x4AerXV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 11651f8cb2e88372d4ed523d909514dc9a613ea3
commit: ff5f643de0bf27874c4033cd57a0bd034b5c7d11 [1963/7726] drm/imagination: Add GEM and VM related code
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20231215/202312150042.9x4AerXV-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312150042.9x4AerXV-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/202312150042.9x4AerXV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/imagination/pvr_mmu.c:170: warning: Excess struct member 'pvr_dev' description in 'pvr_mmu_backing_page'
drivers/gpu/drm/imagination/pvr_mmu.c:285: warning: Function parameter or member 'flags' not described in 'pvr_mmu_backing_page_sync'
>> drivers/gpu/drm/imagination/pvr_mmu.c:1390: warning: Excess struct member 'sgt' description in 'pvr_mmu_op_context'
>> drivers/gpu/drm/imagination/pvr_mmu.c:1390: warning: Excess struct member 'sgt_offset' description in 'pvr_mmu_op_context'
>> drivers/gpu/drm/imagination/pvr_mmu.c:1390: warning: Excess struct member 'l1_prealloc_tables' description in 'pvr_mmu_op_context'
>> drivers/gpu/drm/imagination/pvr_mmu.c:1390: warning: Excess struct member 'l0_prealloc_tables' description in 'pvr_mmu_op_context'
>> drivers/gpu/drm/imagination/pvr_mmu.c:1390: warning: Excess struct member 'l1_free_tables' description in 'pvr_mmu_op_context'
>> drivers/gpu/drm/imagination/pvr_mmu.c:1390: warning: Excess struct member 'l0_free_tables' description in 'pvr_mmu_op_context'
vim +170 drivers/gpu/drm/imagination/pvr_mmu.c
155
156 /**
157 * struct pvr_mmu_backing_page - Represents a single page used to back a page
158 * table of any level.
159 * @dma_addr: DMA address of this page.
160 * @host_ptr: CPU address of this page.
161 * @pvr_dev: The PowerVR device to which this page is associated. **For
162 * internal use only.**
163 */
164 struct pvr_mmu_backing_page {
165 dma_addr_t dma_addr;
166 void *host_ptr;
167 /* private: internal use only */
168 struct page *raw_page;
169 struct pvr_device *pvr_dev;
> 170 };
171
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-14 16:19 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=202312150042.9x4AerXV-lkp@intel.com \
--to=lkp@intel.com \
--cc=donald.robson@imgtec.com \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=matt.coster@imgtec.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sarah.walker@imgtec.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