From: kernel test robot <lkp@intel.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
antoniu.miclaus@analog.com, alexandre.belloni@bootlin.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, jdelvare@suse.com, linux@roeck-us.net
Cc: oe-kbuild-all@lists.linux.dev, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org,
Ibrahim Tilki <Ibrahim.Tilki@analog.com>,
Zeynep Arslanbenzer <Zeynep.Arslanbenzer@analog.com>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH v7 1/2] drivers: rtc: add max313xx series rtc driver
Date: Wed, 21 Feb 2024 06:56:02 +0800 [thread overview]
Message-ID: <202402210633.wquhPF22-lkp@intel.com> (raw)
In-Reply-To: <20240219221827.3821415-2-chris.packham@alliedtelesis.co.nz>
Hi Chris,
kernel test robot noticed the following build warnings:
[auto build test WARNING on abelloni/rtc-next]
[also build test WARNING on linus/master v6.8-rc5 next-20240220]
[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/Chris-Packham/drivers-rtc-add-max313xx-series-rtc-driver/20240220-062057
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
patch link: https://lore.kernel.org/r/20240219221827.3821415-2-chris.packham%40alliedtelesis.co.nz
patch subject: [PATCH v7 1/2] drivers: rtc: add max313xx series rtc driver
config: x86_64-randconfig-123-20240220 (https://download.01.org/0day-ci/archive/20240221/202402210633.wquhPF22-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/20240221/202402210633.wquhPF22-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/202402210633.wquhPF22-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/rtc/rtc-max31335.c:727:22: sparse: sparse: symbol 'max313xx_clk_init' was not declared. Should it be static?
>> drivers/rtc/rtc-max31335.c:750:21: sparse: sparse: symbol 'max313xx_nvmem_cfg' was not declared. Should it be static?
vim +/max313xx_clk_init +727 drivers/rtc/rtc-max31335.c
726
> 727 struct clk_init_data max313xx_clk_init = {
728 .name = "max313xx-clkout",
729 .ops = &max313xx_clkout_ops,
730 };
731
732 static int max313xx_nvmem_reg_read(void *priv, unsigned int offset,
733 void *val, size_t bytes)
734 {
735 struct max313xx *rtc = priv;
736 unsigned int reg = rtc->chip->ram_reg + offset;
737
738 return regmap_bulk_read(rtc->regmap, reg, val, bytes);
739 }
740
741 static int max313xx_nvmem_reg_write(void *priv, unsigned int offset,
742 void *val, size_t bytes)
743 {
744 struct max313xx *rtc = priv;
745 unsigned int reg = rtc->chip->ram_reg + offset;
746
747 return regmap_bulk_write(rtc->regmap, reg, val, bytes);
748 }
749
> 750 struct nvmem_config max313xx_nvmem_cfg = {
751 .reg_read = max313xx_nvmem_reg_read,
752 .reg_write = max313xx_nvmem_reg_write,
753 .word_size = 8,
754 };
755
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-20 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 22:18 [PATCH v7 0/2] drivers: rtc: add max313xx series rtc driver Chris Packham
2024-02-19 22:18 ` [PATCH v7 1/2] " Chris Packham
2024-02-20 19:42 ` Guenter Roeck
2024-02-20 20:07 ` Chris Packham
2024-02-20 22:56 ` kernel test robot [this message]
2024-02-21 18:04 ` kernel test robot
2024-02-19 22:18 ` [PATCH v7 2/2] dt-bindings: rtc: add max313xx RTCs Chris Packham
2024-02-20 19:21 ` Conor Dooley
2024-02-20 20:11 ` Chris Packham
2024-02-21 20:02 ` Conor Dooley
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=202402210633.wquhPF22-lkp@intel.com \
--to=lkp@intel.com \
--cc=Ibrahim.Tilki@analog.com \
--cc=Zeynep.Arslanbenzer@analog.com \
--cc=alexandre.belloni@bootlin.com \
--cc=antoniu.miclaus@analog.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@kernel.org \
/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