From: hejunhao <hejunhao3@huawei.com>
To: kernel test robot <lkp@intel.com>, <will@kernel.org>,
<jonathan.cameron@huawei.com>, <linux-kernel@vger.kernel.org>,
<mark.rutland@arm.com>
Cc: <oe-kbuild-all@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<linux-doc@vger.kernel.org>, <linuxarm@huawei.com>,
<yangyicong@huawei.com>, <shenyang39@huawei.com>,
<prime.zeng@hisilicon.com>
Subject: Re: [PATCH 1/3] drivers/perf: hisi: Add support for HiSilicon H60PA and PAv3 PMU driver
Date: Sat, 27 May 2023 16:31:24 +0800 [thread overview]
Message-ID: <6e7afde3-1358-ddcf-fca1-bd0056285cd8@huawei.com> (raw)
In-Reply-To: <202305241109.DJKYvjGM-lkp@intel.com>
On 2023/5/24 12:28, kernel test robot wrote:
> Hi Junhao,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v6.4-rc3 next-20230523]
> [cannot apply to soc/for-next]
> [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/Junhao-He/drivers-perf-hisi-Add-support-for-HiSilicon-H60PA-and-PAv3-PMU-driver/20230523-215041
> base: linus/master
> patch link: https://lore.kernel.org/r/20230523131825.6102-2-hejunhao3%40huawei.com
> patch subject: [PATCH 1/3] drivers/perf: hisi: Add support for HiSilicon H60PA and PAv3 PMU driver
> config: arm64-allyesconfig
> compiler: aarch64-linux-gcc (GCC) 12.1.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://github.com/intel-lab-lkp/linux/commit/f89c838447a57f5b51474a6aea981acbe68f73b9
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Junhao-He/drivers-perf-hisi-Add-support-for-HiSilicon-H60PA-and-PAv3-PMU-driver/20230523-215041
> git checkout f89c838447a57f5b51474a6aea981acbe68f73b9
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/perf/
>
> 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/202305241109.DJKYvjGM-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from drivers/perf/hisilicon/hisi_uncore_pmu.c:21:
>>> drivers/perf/hisilicon/hisi_uncore_pmu.h:140:5: warning: no previous prototype for 'hisi_uncore_pmu_ver2idx' [-Wmissing-prototypes]
> 140 | int hisi_uncore_pmu_ver2idx(struct hisi_pmu *pmu)
> | ^~~~~~~~~~~~~~~~~~~~~~~
Thanks, Will fix in next version.
>
> vim +/hisi_uncore_pmu_ver2idx +140 drivers/perf/hisilicon/hisi_uncore_pmu.h
>
> 139
> > 140 int hisi_uncore_pmu_ver2idx(struct hisi_pmu *pmu)
>
next prev parent reply other threads:[~2023-05-27 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 13:18 [PATCH 0/3] Add support for HiSilicon SoC uncore PMU Junhao He
2023-05-23 13:18 ` [PATCH 1/3] drivers/perf: hisi: Add support for HiSilicon H60PA and PAv3 PMU driver Junhao He
2023-05-24 4:28 ` kernel test robot
2023-05-27 8:31 ` hejunhao [this message]
2023-05-25 13:04 ` Yicong Yang
2023-05-27 9:29 ` hejunhao
2023-05-23 13:18 ` [PATCH 2/3] drivers/perf: hisi: Add support for HiSilicon UC " Junhao He
2023-05-25 13:39 ` Yicong Yang
2023-05-27 9:37 ` hejunhao
2023-05-23 13:18 ` [PATCH 3/3] docs: perf: Add new description for HiSilicon UC PMU Junhao He
2023-05-25 13:41 ` Yicong Yang
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=6e7afde3-1358-ddcf-fca1-bd0056285cd8@huawei.com \
--to=hejunhao3@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=prime.zeng@hisilicon.com \
--cc=shenyang39@huawei.com \
--cc=will@kernel.org \
--cc=yangyicong@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®