From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Stafford Horne <shorne@gmail.com>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: [stffrdhrn:or1k-rseq 5/5] tools/testing/selftests/rseq/rseq-or1k.h: rseq-or1k-bits.h is included more than once.
Date: Fri, 27 Dec 2024 09:31:09 +0800 [thread overview]
Message-ID: <Z24DXSKP9VYu570T@rli9-mobl> (raw)
In-Reply-To: <202412270840.23RVr7Xf-lkp@intel.com>
On Fri, Dec 27, 2024 at 08:56:31AM +0800, kernel test robot wrote:
> tree: https://github.com/stffrdhrn/linux.git or1k-rseq
> head: 1fa73dd6c2d3c915af3f33929f8a9b437d7cd112
> commit: 1fa73dd6c2d3c915af3f33929f8a9b437d7cd112 [5/5] rseq/selftests: Add support for OpenRISC
> compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
>
> 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/202412270840.23RVr7Xf-lkp@intel.com/
>
> includecheck warnings: (new ones prefixed by >>)
> >> tools/testing/selftests/rseq/rseq-or1k.h: rseq-or1k-bits.h is included more than once.
Sorry, kindly ignore this report, it should be a false positive.
>
> vim +158 tools/testing/selftests/rseq/rseq-or1k.h
>
> 155
> 156 #define RSEQ_TEMPLATE_CPU_ID
> 157 #define RSEQ_TEMPLATE_MO_RELAXED
> > 158 #include "rseq-or1k-bits.h"
> 159 #undef RSEQ_TEMPLATE_MO_RELAXED
> 160
> 161 #define RSEQ_TEMPLATE_MO_RELEASE
> > 162 #include "rseq-or1k-bits.h"
> 163 #undef RSEQ_TEMPLATE_MO_RELEASE
> 164 #undef RSEQ_TEMPLATE_CPU_ID
> 165
> 166 /* Per-mm-cid indexing. */
> 167
> 168 #define RSEQ_TEMPLATE_MM_CID
> 169 #define RSEQ_TEMPLATE_MO_RELAXED
> > 170 #include "rseq-or1k-bits.h"
> 171 #undef RSEQ_TEMPLATE_MO_RELAXED
> 172
> 173 #define RSEQ_TEMPLATE_MO_RELEASE
> > 174 #include "rseq-or1k-bits.h"
> 175 #undef RSEQ_TEMPLATE_MO_RELEASE
> 176 #undef RSEQ_TEMPLATE_MM_CID
> 177
> 178 /* APIs which are not based on cpu ids. */
> 179
> 180 #define RSEQ_TEMPLATE_CPU_ID_NONE
> 181 #define RSEQ_TEMPLATE_MO_RELAXED
> > 182 #include "rseq-or1k-bits.h"
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2024-12-27 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 0:56 [stffrdhrn:or1k-rseq 5/5] tools/testing/selftests/rseq/rseq-or1k.h: rseq-or1k-bits.h is included more than once kernel test robot
2024-12-27 1:31 ` Philip Li [this message]
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=Z24DXSKP9VYu570T@rli9-mobl \
--to=philip.li@intel.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shorne@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 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.