From: kernel test robot <lkp@intel.com>
To: Takaya Saeki <takayas@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, selinux@vger.kernel.org,
Paul Moore <paul@paul-moore.com>
Subject: [pcmoore-selinux:next 6/7] security/selinux/ss/services.c: linux/parser.h is included more than once.
Date: Sat, 12 Apr 2025 19:33:52 +0800 [thread overview]
Message-ID: <202504121945.Q0GDD0sG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git next
head: 5d7ddc59b3d89b724a5aa8f30d0db94ff8d2d93f
commit: 8716451a4e57cc82f3656d7a71b67d3b5831ef3f [6/7] selinux: support wildcard match in genfscon
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
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/202504121945.Q0GDD0sG-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> security/selinux/ss/services.c: linux/parser.h is included more than once.
vim +49 security/selinux/ss/services.c
> 49 #include <linux/parser.h>
50 #include <linux/vmalloc.h>
51 #include <linux/lsm_hooks.h>
> 52 #include <linux/parser.h>
53 #include <net/netlabel.h>
54
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-04-12 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 11:33 kernel test robot [this message]
2025-04-12 15:42 ` [pcmoore-selinux:next 6/7] security/selinux/ss/services.c: linux/parser.h is included more than once Paul Moore
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=202504121945.Q0GDD0sG-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=takayas@chromium.org \
/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.