From: kernel test robot <lkp@intel.com>
To: Sarah Walker <sarah.walker@imgtec.com>
Cc: 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>,
Donald Robson <donald.robson@imgtec.com>
Subject: [linux-next:master 2075/4102] drivers/gpu/drm/imagination/pvr_fw_trace.c:205:37: warning: 'pvr_fw_trace_group_mask_fops' defined but not used
Date: Thu, 30 Nov 2023 20:24:49 +0800 [thread overview]
Message-ID: <202311302054.MVYPxFCE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3cd3fe06ff81cfb3a969acb12a56796cff5af23d
commit: cb56cd61086645e46cc54d1837de803b1c471df6 [2075/4102] drm/imagination: Add firmware trace to debugfs
config: arm64-randconfig-r051-20231130 (https://download.01.org/0day-ci/archive/20231130/202311302054.MVYPxFCE-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231130/202311302054.MVYPxFCE-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/202311302054.MVYPxFCE-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/imagination/pvr_fw_trace.c:205:37: warning: 'pvr_fw_trace_group_mask_fops' defined but not used [-Wunused-const-variable=]
205 | static const struct file_operations pvr_fw_trace_group_mask_fops = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/pvr_fw_trace_group_mask_fops +205 drivers/gpu/drm/imagination/pvr_fw_trace.c
204
> 205 static const struct file_operations pvr_fw_trace_group_mask_fops = {
206 .owner = THIS_MODULE,
207 .open = fw_trace_group_mask_open,
208 .read = seq_read,
209 .write = fw_trace_group_mask_write,
210 .llseek = default_llseek,
211 .release = single_release,
212 };
213
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-30 12:25 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=202311302054.MVYPxFCE-lkp@intel.com \
--to=lkp@intel.com \
--cc=donald.robson@imgtec.com \
--cc=linux-mm@kvack.org \
--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