mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Qinxin Xia <xiaqinxin@huawei.com>,
	21cnbao@gmail.com, m.szyprowski@samsung.com,
	robin.murphy@arm.com
Cc: oe-kbuild-all@lists.linux.dev, prime.zeng@huawei.com,
	fanghao11@huawei.com, linux-kernel@vger.kernel.org,
	linuxarm@huawei.com, xiaqinxin@huawei.com,
	wangzhou1@hisilicon.com
Subject: Re: [PATCH v2] tools/dma: move dma_map_benchmark from selftests to tools/dma
Date: Sun, 19 Oct 2025 12:28:56 +0800	[thread overview]
Message-ID: <202510191133.ThgrGhqL-lkp@intel.com> (raw)
In-Reply-To: <20251018101402.3079372-1-xiaqinxin@huawei.com>

Hi Qinxin,

kernel test robot noticed the following build errors:

[auto build test ERROR on shuah-kselftest/next]
[also build test ERROR on shuah-kselftest/fixes linus/master v6.18-rc1 next-20251017]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Qinxin-Xia/tools-dma-move-dma_map_benchmark-from-selftests-to-tools-dma/20251018-181628
base:   https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:    https://lore.kernel.org/r/20251018101402.3079372-1-xiaqinxin%40huawei.com
patch subject: [PATCH v2] tools/dma: move dma_map_benchmark from selftests to tools/dma
config: x86_64-buildonly-randconfig-002-20251019 (https://download.01.org/0day-ci/archive/20251019/202510191133.ThgrGhqL-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251019/202510191133.ThgrGhqL-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/oe-kbuild-all/202510191133.ThgrGhqL-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from <command-line>:
>> ./usr/include/linux/map_benchmark.h:19:9: error: unknown type name '__u64'
      19 |         __u64 avg_map_100ns; /* average map latency in 100ns */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:20:9: error: unknown type name '__u64'
      20 |         __u64 map_stddev; /* standard deviation of map latency */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:21:9: error: unknown type name '__u64'
      21 |         __u64 avg_unmap_100ns; /* as above */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:22:9: error: unknown type name '__u64'
      22 |         __u64 unmap_stddev;
         |         ^~~~~
>> ./usr/include/linux/map_benchmark.h:23:9: error: unknown type name '__u32'
      23 |         __u32 threads; /* how many threads will do map/unmap in parallel */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:24:9: error: unknown type name '__u32'
      24 |         __u32 seconds; /* how long the test will last */
         |         ^~~~~
>> ./usr/include/linux/map_benchmark.h:25:9: error: unknown type name '__s32'
      25 |         __s32 node; /* which numa node this benchmark will run on */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:26:9: error: unknown type name '__u32'
      26 |         __u32 dma_bits; /* DMA addressing capability */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:27:9: error: unknown type name '__u32'
      27 |         __u32 dma_dir; /* DMA data direction */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:28:9: error: unknown type name '__u32'
      28 |         __u32 dma_trans_ns; /* time for DMA transmission in ns */
         |         ^~~~~
   ./usr/include/linux/map_benchmark.h:29:9: error: unknown type name '__u32'
      29 |         __u32 granule;  /* how many PAGE_SIZE will do map/unmap once a time */
         |         ^~~~~
>> ./usr/include/linux/map_benchmark.h:30:9: error: unknown type name '__u8'
      30 |         __u8 expansion[76]; /* For future use */
         |         ^~~~

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

      reply	other threads:[~2025-10-19  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 10:14 Qinxin Xia
2025-10-19  4:28 ` kernel test robot [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=202510191133.ThgrGhqL-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=21cnbao@gmail.com \
    --cc=fanghao11@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=m.szyprowski@samsung.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=prime.zeng@huawei.com \
    --cc=robin.murphy@arm.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=xiaqinxin@huawei.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

all inboxes | Powered by JetHome®