From: kernel test robot <rong.a.chen@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: [tip:tmp.tmp2 223/364] fs/namei.c: linux/audit.h is included more than once.
Date: Tue, 15 Jun 2021 09:05:08 +0800 [thread overview]
Message-ID: <20210615010508.GI237458@shao2-debian> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tmp.tmp2
head: adcceb5eb7aee38e4a9c15bdf599655f0e1b1324
commit: 25f492130c2aeb29ca88f0207dd616730af84ea9 [223/364] sched/headers, audit: Uninline audit_inode_child()
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> fs/namei.c: linux/audit.h is included more than once.
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: [tip:tmp.tmp2 223/364] fs/namei.c: linux/audit.h is included more than once.
Date: Tue, 15 Jun 2021 09:05:08 +0800 [thread overview]
Message-ID: <20210615010508.GI237458@shao2-debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tmp.tmp2
head: adcceb5eb7aee38e4a9c15bdf599655f0e1b1324
commit: 25f492130c2aeb29ca88f0207dd616730af84ea9 [223/364] sched/headers, audit: Uninline audit_inode_child()
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> fs/namei.c: linux/audit.h is included more than once.
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2021-06-15 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:05 kernel test robot [this message]
2021-06-15 1:05 ` [tip:tmp.tmp2 223/364] fs/namei.c: linux/audit.h is included more than once kernel test robot
2021-06-15 1:06 ` [RFC PATCH tip] sched/headers, audit: fix duplicated inclusion kernel test robot
2021-06-15 1:06 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-06-13 21:18 [tip:tmp.tmp2 223/364] fs/namei.c: linux/audit.h is included more than once kernel test robot
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=20210615010508.GI237458@shao2-debian \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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.