From: kernel test robot <lkp@intel.com>
To: "sw.multimedia" <sw.multimedia@starfivetech.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Emil Renner Berthing" <emil.renner.berthing@canonical.com>,
"jack.zhu" <jack.zhu@starfivetech.com>,
"keith.zhao" <keith.zhao@starfivetech.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"José Expósito" <jose.exposito89@gmail.com>
Subject: [esmil:visionfive 53/59] drivers/gpu/drm/starfive/starfive_drm_gem.c:17:42: warning: 'mmap_mem_ops' defined but not used
Date: Mon, 21 Aug 2023 17:56:13 +0800 [thread overview]
Message-ID: <202308211751.mGGf4GC1-lkp@intel.com> (raw)
tree: https://github.com/esmil/linux visionfive
head: a6b7b4fc1e5719be8b5897f31b9326100f945d51
commit: cd449db0cf6e75db28c9fcefc5a588d39265c167 [53/59] drm/starfive: Add StarFive drm driver
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20230821/202308211751.mGGf4GC1-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230821/202308211751.mGGf4GC1-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/202308211751.mGGf4GC1-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/starfive/starfive_drm_gem.c:17:42: warning: 'mmap_mem_ops' defined but not used [-Wunused-const-variable=]
17 | static const struct vm_operations_struct mmap_mem_ops = {
| ^~~~~~~~~~~~
vim +/mmap_mem_ops +17 drivers/gpu/drm/starfive/starfive_drm_gem.c
15
16 static const struct drm_gem_object_funcs starfive_gem_object_funcs;
> 17 static const struct vm_operations_struct mmap_mem_ops = {
18 #ifdef CONFIG_HAVE_IOREMAP_PROT
19 .access = generic_access_phys
20 #endif
21 };
22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-21 9:56 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=202308211751.mGGf4GC1-lkp@intel.com \
--to=lkp@intel.com \
--cc=emil.renner.berthing@canonical.com \
--cc=geert@linux-m68k.org \
--cc=jack.zhu@starfivetech.com \
--cc=jose.exposito89@gmail.com \
--cc=keith.zhao@starfivetech.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sw.multimedia@starfivetech.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 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.