public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: include/linux/sync_core.h: asm/sync_core.h is included more than once.
Date: Fri, 20 Sep 2024 08:45:18 +0800	[thread overview]
Message-ID: <202409200859.fKF5Xs8a-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   2004cef11ea072838f99bd95cefa5c8e45df0847
commit: 4ff4c745a16c4c151a71863420811e7f406c3ec2 locking: Introduce prepare_sync_core_cmd()
date:   7 months ago
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)

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/202409200859.fKF5Xs8a-lkp@intel.com/

includecheck warnings: (new ones prefixed by >>)
>> include/linux/sync_core.h: asm/sync_core.h is included more than once.

vim +6 include/linux/sync_core.h

     4	
     5	#ifdef CONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
   > 6	#include <asm/sync_core.h>
     7	#else
     8	/*
     9	 * This is a dummy sync_core_before_usermode() implementation that can be used
    10	 * on all architectures which return to user-space through core serializing
    11	 * instructions.
    12	 * If your architecture returns to user-space through non-core-serializing
    13	 * instructions, you need to write your own functions.
    14	 */
    15	static inline void sync_core_before_usermode(void)
    16	{
    17	}
    18	#endif
    19	
    20	#ifdef CONFIG_ARCH_HAS_PREPARE_SYNC_CORE_CMD
  > 21	#include <asm/sync_core.h>
    22	#else
    23	/*
    24	 * This is a dummy prepare_sync_core_cmd() implementation that can be used on
    25	 * all architectures which provide unconditional core serializing instructions
    26	 * in switch_mm().
    27	 * If your architecture doesn't provide such core serializing instructions in
    28	 * switch_mm(), you may need to write your own functions.
    29	 */
    30	static inline void prepare_sync_core_cmd(struct mm_struct *mm)
    31	{
    32	}
    33	#endif
    34	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-09-20  0:45 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=202409200859.fKF5Xs8a-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=palmer@rivosinc.com \
    --cc=parri.andrea@gmail.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