From: kernel test robot <yujie.liu@intel.com>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: <oe-kbuild-all@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-nonmm-unstable 7/20] kernel/signal.c: linux/file.h is included more than once.
Date: Tue, 11 Jul 2023 14:53:49 +0800 [thread overview]
Message-ID: <202307081626.VOmT8STW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
head: cdd54ce0ffc0c99482337abc8f65f4f7058e1115
commit: 0646c9dc794fe4d3ba48da9dad37300e430e6eff [7/20] signal: print comm and exe name on fatal signals
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202307081626.VOmT8STW-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> kernel/signal.c: linux/file.h is included more than once.
vim +23 kernel/signal.c
> 23 #include <linux/file.h>
24 #include <linux/fs.h>
25 #include <linux/mm.h>
26 #include <linux/proc_fs.h>
27 #include <linux/tty.h>
> 28 #include <linux/file.h>
29 #include <linux/binfmts.h>
30 #include <linux/coredump.h>
31 #include <linux/security.h>
32 #include <linux/syscalls.h>
33 #include <linux/ptrace.h>
34 #include <linux/signal.h>
35 #include <linux/signalfd.h>
36 #include <linux/ratelimit.h>
37 #include <linux/task_work.h>
38 #include <linux/capability.h>
39 #include <linux/freezer.h>
40 #include <linux/pid_namespace.h>
41 #include <linux/nsproxy.h>
42 #include <linux/user_namespace.h>
43 #include <linux/uprobes.h>
44 #include <linux/compat.h>
45 #include <linux/cn_proc.h>
46 #include <linux/compiler.h>
47 #include <linux/posix-timers.h>
48 #include <linux/cgroup.h>
49 #include <linux/audit.h>
50 #include <linux/sysctl.h>
51
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-11 6:58 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=202307081626.VOmT8STW-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vincent.whitchurch@axis.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