From: kernel test robot <lkp@intel.com>
To: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/2] block: introduce helper function to calculate bps budgt
Date: Sat, 11 May 2024 19:15:08 +0800 [thread overview]
Message-ID: <202405111926.ww1PplNP-lkp@intel.com> (raw)
In-Reply-To: <20240509023937.1090421-2-zhaoyang.huang@unisoc.com>
Hi zhaoyang.huang,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe-block/for-next]
[also build test WARNING on akpm-mm/mm-everything linus/master v6.9-rc7]
[cannot apply to next-20240510]
[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/zhaoyang-huang/block-introduce-helper-function-to-calculate-bps-budgt/20240509-104233
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20240509023937.1090421-2-zhaoyang.huang%40unisoc.com
patch subject: [RFC PATCH 1/2] block: introduce helper function to calculate bps budgt
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20240511/202405111926.ww1PplNP-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project b910bebc300dafb30569cecc3017b446ea8eafa0)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240511/202405111926.ww1PplNP-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/202405111926.ww1PplNP-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from mm/readahead.c:116:
In file included from include/linux/blkdev.h:9:
In file included from include/linux/blk_types.h:10:
In file included from include/linux/bvec.h:10:
In file included from include/linux/highmem.h:8:
In file included from include/linux/cacheflush.h:5:
In file included from arch/arm/include/asm/cacheflush.h:10:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
In file included from mm/readahead.c:127:
include/linux/mm_inline.h:47:41: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
47 | __mod_lruvec_state(lruvec, NR_LRU_BASE + lru, nr_pages);
| ~~~~~~~~~~~ ^ ~~~
include/linux/mm_inline.h:49:22: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
49 | NR_ZONE_LRU_BASE + lru, nr_pages);
| ~~~~~~~~~~~~~~~~ ^ ~~~
In file included from mm/readahead.c:128:
>> include/linux/blk-cgroup.h:55:9: warning: implicit conversion from 'u64' (aka 'unsigned long long') to 'unsigned long' changes value from 18446744073709551615 to 4294967295 [-Wconstant-conversion]
55 | return U64_MAX;
| ~~~~~~ ^~~~~~~
include/linux/limits.h:25:19: note: expanded from macro 'U64_MAX'
25 | #define U64_MAX ((u64)~0ULL)
| ^~~~~~~~~~
4 warnings generated.
--
In file included from mm/backing-dev.c:3:
In file included from include/linux/blkdev.h:9:
In file included from include/linux/blk_types.h:10:
In file included from include/linux/bvec.h:10:
In file included from include/linux/highmem.h:8:
In file included from include/linux/cacheflush.h:5:
In file included from arch/arm/include/asm/cacheflush.h:10:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
In file included from mm/backing-dev.c:8:
>> include/linux/blk-cgroup.h:55:9: warning: implicit conversion from 'u64' (aka 'unsigned long long') to 'unsigned long' changes value from 18446744073709551615 to 4294967295 [-Wconstant-conversion]
55 | return U64_MAX;
| ~~~~~~ ^~~~~~~
include/linux/limits.h:25:19: note: expanded from macro 'U64_MAX'
25 | #define U64_MAX ((u64)~0ULL)
| ^~~~~~~~~~
2 warnings generated.
vim +55 include/linux/blk-cgroup.h
49
50 #ifdef CONFIG_BLK_DEV_THROTTLING
51 unsigned long blk_throttle_budgt(struct block_device *bdev);
52 #else
53 static inline unsigned long blk_throttle_budgt(struct block_device *bdev)
54 {
> 55 return U64_MAX;
56 }
57 #endif
58 int blkcg_set_fc_appid(char *app_id, u64 cgrp_id, size_t app_id_len);
59 char *blkcg_get_fc_appid(struct bio *bio);
60
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2024-05-11 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240509023937.1090421-2-zhaoyang.huang@unisoc.com>
2024-05-11 11:15 ` kernel test robot [this message]
[not found] <20240515012350.1166350-2-zhaoyang.huang@unisoc.com>
2024-05-16 10:33 ` [RFC PATCH 1/2] block: introduce helper function to calculate bps budgt 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=202405111926.ww1PplNP-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhaoyang.huang@unisoc.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