From: kernel test robot <lkp@intel.com>
To: Jagath Jog J <jagathjog1996@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [linux-next:master 10319/16858] drivers/iio/imu/bmi323/bmi323_spi.c:44:28: sparse: sparse: symbol 'bmi323_spi_regmap_config' was not declared. Should it be static?
Date: Sat, 11 Nov 2023 09:50:15 +0800 [thread overview]
Message-ID: <202311110902.HjNmBOUN-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8728c14129df7a6e29188a2e737b4774fb200953
commit: b512c767e7bcef308ee5b038405debf9baa9c579 [10319/16858] iio: imu: Add driver for BMI323 IMU
config: i386-randconfig-063-20231111 (https://download.01.org/0day-ci/archive/20231111/202311110902.HjNmBOUN-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231111/202311110902.HjNmBOUN-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/202311110902.HjNmBOUN-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/imu/bmi323/bmi323_spi.c:44:28: sparse: sparse: symbol 'bmi323_spi_regmap_config' was not declared. Should it be static?
vim +/bmi323_spi_regmap_config +44 drivers/iio/imu/bmi323/bmi323_spi.c
43
> 44 const struct regmap_config bmi323_spi_regmap_config = {
45 .reg_bits = 8,
46 .val_bits = 16,
47 .pad_bits = 8,
48 .read_flag_mask = BIT(7),
49 .max_register = BMI323_CFG_RES_REG,
50 .val_format_endian = REGMAP_ENDIAN_LITTLE,
51 };
52
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-11 1:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202311110902.HjNmBOUN-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=jagathjog1996@gmail.com \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox