From: kernel test robot <lkp@intel.com>
To: "Willem-Jan de Hoog" <arinc9.unal@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Willem-Jan de Hoog" <wdehoog@exalondelft.nl>,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
erkin.bozoglu@xeront.com
Subject: Re: [PATCH 1/2] firmware: bcm47xx_nvram: allow to read from buffered nvram data
Date: Thu, 9 Feb 2023 00:49:23 +0800 [thread overview]
Message-ID: <202302090020.TxUXGMeJ-lkp@intel.com> (raw)
In-Reply-To: <20230206100502.20243-2-wdehoog@exalondelft.nl>
Hi Willem-Jan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.2-rc7 next-20230208]
[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/Willem-Jan-de-Hoog/firmware-bcm47xx_nvram-allow-to-read-from-buffered-nvram-data/20230206-180737
patch link: https://lore.kernel.org/r/20230206100502.20243-2-wdehoog%40exalondelft.nl
patch subject: [PATCH 1/2] firmware: bcm47xx_nvram: allow to read from buffered nvram data
config: x86_64-randconfig-a006-20230206 (https://download.01.org/0day-ci/archive/20230209/202302090020.TxUXGMeJ-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
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/763f6661565b50b967e4f22e41cf46d27e14e58f
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Willem-Jan-de-Hoog/firmware-bcm47xx_nvram-allow-to-read-from-buffered-nvram-data/20230206-180737
git checkout 763f6661565b50b967e4f22e41cf46d27e14e58f
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c:12:
>> include/linux/bcm47xx_nvram.h:56:2: error: expected identifier or '('
}:
^
In file included from drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c:14:
In file included from drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h:9:
In file included from include/linux/net.h:24:
In file included from include/linux/mm.h:15:
>> include/linux/mmap_lock.h:28:6: error: use of undeclared identifier '__tracepoint_mmap_lock_start_locking'; did you mean '__tracepoint_mmap_lock_released'?
if (tracepoint_enabled(mmap_lock_start_locking))
^
include/linux/tracepoint-defs.h:85:21: note: expanded from macro 'tracepoint_enabled'
static_key_false(&(__tracepoint_##tp).key)
^
<scratch space>:48:1: note: expanded from here
__tracepoint_mmap_lock_start_locking
^
include/linux/mmap_lock.h:16:1: note: '__tracepoint_mmap_lock_released' declared here
DECLARE_TRACEPOINT(mmap_lock_released);
^
include/linux/tracepoint-defs.h:81:27: note: expanded from macro 'DECLARE_TRACEPOINT'
extern struct tracepoint __tracepoint_##tp
^
<scratch space>:47:1: note: expanded from here
__tracepoint_mmap_lock_released
^
2 errors generated.
vim +56 include/linux/bcm47xx_nvram.h
52
53 static inline int bcm47xx_nvram_read(unsigned int offset, char *val, size_t val_len)
54 {
55 return -ENOTSUPP;
> 56 }:
57 #endif
58
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-02-08 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 10:05 [PATCH 0/2] nvmem: brcm_nvram: use buffered nvram data for cell values Willem-Jan de Hoog
2023-02-06 10:05 ` [PATCH 1/2] firmware: bcm47xx_nvram: allow to read from buffered nvram data Willem-Jan de Hoog
2023-02-07 6:21 ` kernel test robot
2023-02-08 16:49 ` kernel test robot [this message]
2023-02-15 14:50 ` kernel test robot
2023-02-06 10:05 ` [PATCH 2/2] nvmem: brcm_nvram: use bcm47xx buffered data Willem-Jan de Hoog
-- strict thread matches above, loose matches on Subject: below --
2023-02-10 4:47 [PATCH 1/2] firmware: bcm47xx_nvram: allow to read from buffered nvram data 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=202302090020.TxUXGMeJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=arinc.unal@arinc9.com \
--cc=arinc9.unal@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=srinivas.kandagatla@linaro.org \
--cc=wdehoog@exalondelft.nl \
--cc=zajec5@gmail.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 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.