From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [jgunthorpe:mlx5st 11/18] include/arm64/processor.h:194:9: warning: "dma_wmb" redefined
Date: Fri, 01 May 2026 06:04:05 +0200 [thread overview]
Message-ID: <202605010606.I5idaYNP-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jason Gunthorpe <jgg@nvidia.com>
tree: https://github.com/jgunthorpe/linux mlx5st
head: 10504f47dd2777f27b6ce161435b5773b47d5172
commit: 451d6ff0d1cff6767726ec1875df9cdf81d782d0 [11/18] selftests: Add additional kernel functions to tools/include/
:::::: branch date: 8 hours ago
:::::: commit date: 3 days ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260501/202605010606.I5idaYNP-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260501/202605010606.I5idaYNP-lkp@intel.com/reproduce)
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/r/202605010606.I5idaYNP-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from dirty_log_test.c:22:
>> include/arm64/processor.h:194:9: warning: "dma_wmb" redefined
194 | #define dma_wmb() dmb(oshst)
| ^~~~~~~
In file included from tools/testing/selftests/../../../tools/include/asm/barrier.h:8,
from dirty_log_test.c:17:
tools/testing/selftests/../../../tools/include/asm/../../arch/arm64/include/asm/barrier.h:29:9: note: this is the location of the previous definition
29 | #define dma_wmb() asm volatile("dmb oshst" ::: "memory")
| ^~~~~~~
>> include/arm64/processor.h:197:9: warning: "dma_rmb" redefined
197 | #define dma_rmb() dmb(oshld)
| ^~~~~~~
tools/testing/selftests/../../../tools/include/asm/../../arch/arm64/include/asm/barrier.h:28:9: note: this is the location of the previous definition
28 | #define dma_rmb() asm volatile("dmb oshld" ::: "memory")
| ^~~~~~~
cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics
--
In file included from tools/testing/selftests/../../../tools/include/asm/barrier.h:8,
from include/arm64/gic_v5.h:6,
from arm64/no-vgic.c:12:
>> tools/testing/selftests/../../../tools/include/asm/../../arch/arm64/include/asm/barrier.h:28:9: warning: "dma_rmb" redefined
28 | #define dma_rmb() asm volatile("dmb oshld" ::: "memory")
| ^~~~~~~
In file included from arm64/no-vgic.c:10:
include/arm64/processor.h:197:9: note: this is the location of the previous definition
197 | #define dma_rmb() dmb(oshld)
| ^~~~~~~
>> tools/testing/selftests/../../../tools/include/asm/../../arch/arm64/include/asm/barrier.h:29:9: warning: "dma_wmb" redefined
29 | #define dma_wmb() asm volatile("dmb oshst" ::: "memory")
| ^~~~~~~
include/arm64/processor.h:194:9: note: this is the location of the previous definition
194 | #define dma_wmb() dmb(oshst)
| ^~~~~~~
cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-01 4:04 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=202605010606.I5idaYNP-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.