From: kernel test robot <lkp@intel.com>
To: Du Rui <durui@linux.alibaba.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC] dm overlaybd: targets mapping OverlayBD image
Date: Fri, 19 May 2023 21:16:00 +0800 [thread overview]
Message-ID: <202305192021.OsazVl8p-lkp@intel.com> (raw)
In-Reply-To: <9505927dabc3b6695d62dfe1be371b12f5bdebf7.1684491648.git.durui@linux.alibaba.com>
Hi Du,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on device-mapper-dm/for-next]
[also build test WARNING on song-md/md-next linus/master v6.4-rc2 next-20230519]
[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/Du-Rui/dm-overlaybd-targets-mapping-OverlayBD-image/20230519-184235
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
patch link: https://lore.kernel.org/r/9505927dabc3b6695d62dfe1be371b12f5bdebf7.1684491648.git.durui%40linux.alibaba.com
patch subject: [RFC] dm overlaybd: targets mapping OverlayBD image
reproduce:
make versioncheck
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305192021.OsazVl8p-lkp@intel.com/
versioncheck warnings: (new ones prefixed by >>)
INFO PATH=/opt/cross/clang/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
/usr/bin/timeout -k 100 3h /usr/bin/make W=1 --keep-going HOSTCC=gcc-11 CC=gcc-11 -j32 ARCH=x86_64 versioncheck
find ./* \( -name SCCS -o -name BitKeeper -o -name .svn -o -name CVS -o -name .pc -o -name .hg -o -name .git \) -prune -o \
-name '*.[hcS]' -type f -print | sort \
| xargs perl -w ./scripts/checkversion.pl
./drivers/accessibility/speakup/genmap.c: 13 linux/version.h not needed.
./drivers/accessibility/speakup/makemapdata.c: 13 linux/version.h not needed.
>> ./drivers/md/overlaybd/dm-ovbd.c: 3 linux/version.h not needed.
./drivers/net/ethernet/qlogic/qede/qede.h: 10 linux/version.h not needed.
./drivers/net/ethernet/qlogic/qede/qede_ethtool.c: 7 linux/version.h not needed.
./drivers/soc/tegra/cbb/tegra-cbb.c: 19 linux/version.h not needed.
./drivers/soc/tegra/cbb/tegra194-cbb.c: 26 linux/version.h not needed.
./drivers/soc/tegra/cbb/tegra234-cbb.c: 27 linux/version.h not needed.
./drivers/staging/media/atomisp/include/linux/atomisp.h: 23 linux/version.h not needed.
./samples/trace_events/trace_custom_sched.c: 11 linux/version.h not needed.
./sound/soc/codecs/cs42l42.c: 14 linux/version.h not needed.
./tools/lib/bpf/bpf_helpers.h: 289: need linux/version.h
./tools/perf/tests/bpf-script-example.c: 60: need linux/version.h
./tools/perf/tests/bpf-script-test-kbuild.c: 21: need linux/version.h
./tools/perf/tests/bpf-script-test-prologue.c: 49: need linux/version.h
./tools/perf/tests/bpf-script-test-relocation.c: 51: need linux/version.h
./tools/testing/selftests/bpf/progs/dev_cgroup.c: 9 linux/version.h not needed.
./tools/testing/selftests/bpf/progs/netcnt_prog.c: 3 linux/version.h not needed.
./tools/testing/selftests/bpf/progs/test_map_lock.c: 4 linux/version.h not needed.
./tools/testing/selftests/bpf/progs/test_send_signal_kern.c: 4 linux/version.h not needed.
./tools/testing/selftests/bpf/progs/test_spin_lock.c: 4 linux/version.h not needed.
./tools/testing/selftests/bpf/progs/test_tcp_estats.c: 37 linux/version.h not needed.
./tools/testing/selftests/wireguard/qemu/init.c: 27 linux/version.h not needed.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-05-19 13:16 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 10:27 [dm-devel] [RFC] dm overlaybd: targets mapping OverlayBD image Du Rui
2023-05-19 10:27 ` Du Rui
2023-05-19 13:16 ` kernel test robot [this message]
2023-05-19 14:17 ` kernel test robot
2023-05-19 14:17 ` kernel test robot
2023-05-19 14:17 ` kernel test robot
2023-05-19 20:10 ` kernel test robot
2023-05-19 20:34 ` kernel test robot
2023-05-23 17:28 ` [dm-devel] " Mike Snitzer
2023-05-23 17:28 ` Mike Snitzer
2023-05-24 0:56 ` [dm-devel] " Gao Xiang
2023-05-24 0:56 ` Gao Xiang
2023-05-24 6:43 ` Alexander Larsson
2023-05-24 6:43 ` Alexander Larsson
2023-05-24 7:13 ` [dm-devel] " Gao Xiang
2023-05-24 7:13 ` Gao Xiang
2023-05-24 8:11 ` [dm-devel] " Giuseppe Scrivano
2023-05-24 8:11 ` Giuseppe Scrivano
2023-05-24 8:26 ` [dm-devel] " Gao Xiang
2023-05-24 8:26 ` Gao Xiang
2023-05-24 10:48 ` [dm-devel] " Giuseppe Scrivano
2023-05-24 10:48 ` Giuseppe Scrivano
2023-05-24 11:06 ` [dm-devel] " Gao Xiang
2023-05-24 11:06 ` Gao Xiang
2023-05-26 10:28 ` [dm-devel] " Du Rui
2023-05-26 10:28 ` Du Rui
2023-05-26 10:26 ` [dm-devel] " Du Rui
2023-05-26 10:26 ` Du Rui
2023-05-26 16:43 ` [dm-devel] " Gao Xiang
2023-05-26 16:43 ` Gao Xiang
2023-05-27 3:13 ` [dm-devel] " Du Rui
2023-05-27 3:13 ` Du Rui
2023-05-27 4:12 ` [dm-devel] " Gao Xiang
2023-05-27 4:12 ` Gao Xiang
2023-05-24 6:59 ` [dm-devel] " Du Rui
2023-05-24 6:59 ` Du Rui
2023-05-26 10:25 ` [dm-devel] " Du Rui
2023-05-26 10:25 ` Du Rui
2023-05-24 7:24 ` [dm-devel] [RFC PATCH v2] " Du Rui
2023-05-24 7:24 ` Du Rui
2023-05-24 7:40 ` [dm-devel] [RFC PATCH v3] " Du Rui
2023-05-24 7:40 ` Du Rui
2023-05-24 15:37 ` kernel test robot
2023-05-24 16:14 ` 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=202305192021.OsazVl8p-lkp@intel.com \
--to=lkp@intel.com \
--cc=durui@linux.alibaba.com \
--cc=oe-kbuild-all@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.