From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [RFC PATCH tip] sched/headers: Convert task_struct:: fix duplicated inclusion
Date: Mon, 14 Jun 2021 04:55:41 +0800 [thread overview]
Message-ID: <20210613205541.GA40339@679f459111b3> (raw)
In-Reply-To: <202106140428.UOGl0rub-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
CC: x86(a)kernel.org
TO: Ingo Molnar <mingo@kernel.org>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Borislav Petkov <bp@alien8.de>
CC: x86(a)kernel.org
CC: "H. Peter Anvin" <hpa@zytor.com>
CC: Kees Cook <keescook@chromium.org>
CC: Lai Jiangshan <laijs@linux.alibaba.com>
CC: Peter Zijlstra <peterz@infradead.org>
CC: Andy Lutomirski <luto@kernel.org>
CC: Huang Rui <ray.huang@amd.com>
arch/x86/include/asm/processor.h: linux/sched/thread.h is included more than once.
Generated by: scripts/checkincludes.pl
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
processor.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
index 543e9235c7ad2..3e7d6361c8f87 100644
--- a/arch/x86/include/asm/processor.h
+++ b/arch/x86/include/asm/processor.h
@@ -12,7 +12,6 @@ struct mm_struct;
struct io_bitmap;
struct vm86;
-#include <linux/sched/thread.h>
#include <asm/math_emu.h>
#include <asm/segment.h>
next prev parent reply other threads:[~2021-06-13 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 20:55 [tip:tmp.tmp2 42/364] arch/x86/include/asm/processor.h: linux/sched/thread.h is included more than once kernel test robot
2021-06-13 20:55 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 1:02 kernel test robot
2021-06-15 1:03 ` [RFC PATCH tip] sched/headers: Convert task_struct:: fix duplicated inclusion kernel test robot
2021-06-15 1:03 ` 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=20210613205541.GA40339@679f459111b3 \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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.