From: kernel test robot <lkp@intel.com>
To: Deven Bowers <deven.desai@linux.microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Paul Moore <paul@paul-moore.com>,
Fan Wu <wufan@linux.microsoft.com>
Subject: security/ipe/policy_fs.c:21: warning: cannot understand function prototype: 'struct ipefs_file '
Date: Sun, 19 Jan 2025 08:12:37 +0800 [thread overview]
Message-ID: <202501190816.IQ5G26HR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 595523945be0a5a2f12a1c04772383293fbc04a1
commit: 2261306f4a3cea362fc40285e750a801dc0cfbe3 ipe: add userspace interface
date: 5 months ago
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20250119/202501190816.IQ5G26HR-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250119/202501190816.IQ5G26HR-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/202501190816.IQ5G26HR-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> security/ipe/policy_fs.c:21: warning: cannot understand function prototype: 'struct ipefs_file '
>> security/ipe/policy_fs.c:407: warning: cannot understand function prototype: 'const struct ipefs_file policy_subdir[] = '
vim +21 security/ipe/policy_fs.c
17
18 /**
19 * ipefs_file - defines a file in securityfs.
20 */
> 21 struct ipefs_file {
22 const char *name;
23 umode_t access;
24 const struct file_operations *fops;
25 };
26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-19 0:13 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=202501190816.IQ5G26HR-lkp@intel.com \
--to=lkp@intel.com \
--cc=deven.desai@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=wufan@linux.microsoft.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.