From: kernel test robot <lkp@intel.com>
To: Gary Yang <gary.yang@cixtech.com>,
lee@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, p.zabel@pengutronix.de,
peter.chen@cixtech.com
Cc: oe-kbuild-all@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
cix-kernel-upstream@cixtech.com,
Gary Yang <gary.yang@cixtech.com>
Subject: Re: [PATCH v6 2/3] reset: add Sky1 soc reset support
Date: Tue, 3 Feb 2026 21:36:53 +0800 [thread overview]
Message-ID: <202602032143.85yHYNk5-lkp@intel.com> (raw)
In-Reply-To: <20260203022031.4075627-3-gary.yang@cixtech.com>
Hi Gary,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on lee-leds/for-leds-next linus/master pza/reset/next v6.19-rc8 next-20260202]
[cannot apply to pza/imx-drm/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/Gary-Yang/dt-bindings-soc-cix-document-the-simple-mfd-syscon-on-Sky1-SoC/20260203-102331
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20260203022031.4075627-3-gary.yang%40cixtech.com
patch subject: [PATCH v6 2/3] reset: add Sky1 soc reset support
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260203/202602032143.85yHYNk5-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260203/202602032143.85yHYNk5-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/202602032143.85yHYNk5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/reset/reset-sky1-base.c:97:5: warning: no previous prototype for 'sky1_reset_common_probe' [-Wmissing-prototypes]
97 | int sky1_reset_common_probe(struct platform_device *pdev,
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/sky1_reset_common_probe +97 drivers/reset/reset-sky1-base.c
96
> 97 int sky1_reset_common_probe(struct platform_device *pdev,
98 const struct sky1_src_variant *variant)
99 {
100 struct sky1_src *sky1src;
101 struct device *dev = &pdev->dev;
102
103 sky1src = devm_kzalloc(dev, sizeof(*sky1src), GFP_KERNEL);
104 if (!sky1src)
105 return -ENOMEM;
106
107 sky1src->regmap = device_node_to_regmap(dev->parent->of_node);
108 if (IS_ERR(sky1src->regmap)) {
109 dev_err(dev, "Unable to get sky1-src regmap");
110 return PTR_ERR(sky1src->regmap);
111 }
112
113 sky1src->signals = variant->signals;
114 sky1src->rcdev.owner = THIS_MODULE;
115 sky1src->rcdev.nr_resets = variant->signals_num;
116 sky1src->rcdev.ops = &sky1_src_ops;
117 sky1src->rcdev.of_node = dev->parent->of_node;
118 sky1src->rcdev.dev = dev;
119
120 return devm_reset_controller_register(dev, &sky1src->rcdev);
121 }
122 EXPORT_SYMBOL_GPL(sky1_reset_common_probe);
123
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-03 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 2:20 [PATCH v6 0/3] Add support for Cix Sky1 resets Gary Yang
2026-02-03 2:20 ` [PATCH v6 1/3] dt-bindings: soc: cix: document the simple-mfd syscon on Sky1 SoC Gary Yang
2026-02-03 2:20 ` [PATCH v6 2/3] reset: add Sky1 soc reset support Gary Yang
2026-02-03 13:36 ` kernel test robot [this message]
2026-02-03 17:32 ` kernel test robot
2026-02-03 2:20 ` [PATCH v6 3/3] arm64: dts: cix: add support for cix sky1 resets Gary Yang
-- strict thread matches above, loose matches on Subject: below --
2026-02-03 2:10 [PATCH v6 0/3] Add support for Cix Sky1 resets Gary Yang
2026-02-03 2:10 ` [PATCH v6 2/3] reset: add Sky1 soc reset support Gary 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=202602032143.85yHYNk5-lkp@intel.com \
--to=lkp@intel.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary.yang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=p.zabel@pengutronix.de \
--cc=peter.chen@cixtech.com \
--cc=robh@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 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.