From: kernel test robot <lkp@intel.com>
To: Donglin Peng <pengdonglin@sangfor.com.cn>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] bpf: Using binary search to improve the performance of btf_find_by_name_kind
Date: Sat, 9 Sep 2023 16:49:38 +0800 [thread overview]
Message-ID: <202309091645.Le0RojYK-lkp@intel.com> (raw)
In-Reply-To: <20230909055202.306518-1-pengdonglin@sangfor.com.cn>
Hi Donglin,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
[also build test WARNING on bpf/master linus/master v6.5 next-20230908]
[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/Donglin-Peng/bpf-Using-binary-search-to-improve-the-performance-of-btf_find_by_name_kind/20230909-140210
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20230909055202.306518-1-pengdonglin%40sangfor.com.cn
patch subject: [RFC PATCH] bpf: Using binary search to improve the performance of btf_find_by_name_kind
config: x86_64-buildonly-randconfig-005-20230909 (https://download.01.org/0day-ci/archive/20230909/202309091645.Le0RojYK-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230909/202309091645.Le0RojYK-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/202309091645.Le0RojYK-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/bpf/btf.c:557:5: warning: no previous prototype for function 'btf_type_cnt' [-Wmissing-prototypes]
u32 btf_type_cnt(const struct btf *btf)
^
kernel/bpf/btf.c:557:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
u32 btf_type_cnt(const struct btf *btf)
^
static
1 warning generated.
vim +/btf_type_cnt +557 kernel/bpf/btf.c
556
> 557 u32 btf_type_cnt(const struct btf *btf)
558 {
559 return btf->start_id + btf->nr_types;
560 }
561
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2023-09-09 8:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230909055202.306518-1-pengdonglin@sangfor.com.cn>]
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=202309091645.Le0RojYK-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pengdonglin@sangfor.com.cn \
/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