From: kernel test robot <lkp@intel.com>
To: Jon Moeller <jon.moeller@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, "Pan, Kris" <kris.pan@intel.com>
Subject: [intel-lts:4.19/android_s 3638/30000] drivers/platform/x86/sepdk/pax/pax.c:88:31: warning: 'pax_version_ops' defined but not used
Date: Mon, 16 Oct 2023 21:01:47 +0800 [thread overview]
Message-ID: <202310162113.nmC2Keli-lkp@intel.com> (raw)
tree: https://github.com/intel/linux-intel-lts.git 4.19/android_s
head: a0b8c3f924aa72ed5d1892e77377d9144287fc35
commit: fadb19e08fbf603c6b11d9c45dbf33accdd58016 [3638/30000] platform/x86: add sep and socwatch drivers without socperf.
config: i386-buildonly-randconfig-002-20231016 (https://download.01.org/0day-ci/archive/20231016/202310162113.nmC2Keli-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231016/202310162113.nmC2Keli-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/202310162113.nmC2Keli-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/platform/x86/sepdk/pax/pax.c:88:31: warning: 'pax_version_ops' defined but not used [-Wunused-variable]
88 | static struct file_operations pax_version_ops = {
| ^~~~~~~~~~~~~~~
vim +/pax_version_ops +88 drivers/platform/x86/sepdk/pax/pax.c
85
86 static int pax_version_proc_read(struct seq_file *, void *);
87 static int pax_version_proc_open(struct inode *, struct file *);
> 88 static struct file_operations pax_version_ops = {
89 .owner = THIS_MODULE,
90 .open = pax_version_proc_open,
91 .read = seq_read,
92 .llseek = seq_lseek,
93 .release = single_release,
94 };
95
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-16 13:02 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=202310162113.nmC2Keli-lkp@intel.com \
--to=lkp@intel.com \
--cc=jon.moeller@intel.com \
--cc=kris.pan@intel.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.