From: kernel test robot <lkp@intel.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: oe-kbuild-all@lists.linux.dev,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [linux-next:master 10159/11535] drivers/power/sequencing/pwrseq-pcie-m2.c:193:12: warning: assignment to 'struct device_node *' from 'int' makes pointer from integer without a cast
Date: Tue, 07 Apr 2026 11:48:56 +0800 [thread overview]
Message-ID: <202604031945.bEYKHUme-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cc13002a9f984d37906e9476f3e532a8cdd126f5
commit: 3f736aecbdc8e4faf2ed82c981812a6bfc76ea98 [10159/11535] power: sequencing: pcie-m2: Create serdev device for WCN7850 bluetooth
config: sh-randconfig-001-20260403 (https://download.01.org/0day-ci/archive/20260403/202604031945.bEYKHUme-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260403/202604031945.bEYKHUme-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/202604031945.bEYKHUme-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/power/sequencing/pwrseq-pcie-m2.c: In function 'pwrseq_m2_pcie_create_bt_node':
drivers/power/sequencing/pwrseq-pcie-m2.c:191:9: error: implicit declaration of function 'of_changeset_init' [-Werror=implicit-function-declaration]
191 | of_changeset_init(ctx->ocs);
| ^~~~~~~~~~~~~~~~~
drivers/power/sequencing/pwrseq-pcie-m2.c:193:14: error: implicit declaration of function 'of_changeset_create_node' [-Werror=implicit-function-declaration]
193 | np = of_changeset_create_node(ctx->ocs, parent, "bluetooth");
| ^~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/power/sequencing/pwrseq-pcie-m2.c:193:12: warning: assignment to 'struct device_node *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
193 | np = of_changeset_create_node(ctx->ocs, parent, "bluetooth");
| ^
drivers/power/sequencing/pwrseq-pcie-m2.c:200:15: error: implicit declaration of function 'of_changeset_add_prop_string' [-Werror=implicit-function-declaration]
200 | ret = of_changeset_add_prop_string(ctx->ocs, np, "compatible", "qcom,wcn7850-bt");
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/power/sequencing/pwrseq-pcie-m2.c:206:15: error: implicit declaration of function 'of_changeset_apply' [-Werror=implicit-function-declaration]
206 | ret = of_changeset_apply(ctx->ocs);
| ^~~~~~~~~~~~~~~~~~
drivers/power/sequencing/pwrseq-pcie-m2.c:221:9: error: implicit declaration of function 'of_changeset_revert' [-Werror=implicit-function-declaration]
221 | of_changeset_revert(ctx->ocs);
| ^~~~~~~~~~~~~~~~~~~
drivers/power/sequencing/pwrseq-pcie-m2.c:223:9: error: implicit declaration of function 'of_changeset_destroy' [-Werror=implicit-function-declaration]
223 | of_changeset_destroy(ctx->ocs);
| ^~~~~~~~~~~~~~~~~~~~
drivers/power/sequencing/pwrseq-pcie-m2.c: In function 'pwrseq_pcie_m2_register_notifier':
drivers/power/sequencing/pwrseq-pcie-m2.c:368:54: error: 'pci_bus_type' undeclared (first use in this function); did you mean 'pci_pcie_type'?
368 | ret = bus_register_notifier(&pci_bus_type, &ctx->nb);
| ^~~~~~~~~~~~
| pci_pcie_type
drivers/power/sequencing/pwrseq-pcie-m2.c:368:54: note: each undeclared identifier is reported only once for each function it appears in
drivers/power/sequencing/pwrseq-pcie-m2.c: In function 'pwrseq_pcie_m2_remove':
drivers/power/sequencing/pwrseq-pcie-m2.c:455:34: error: 'pci_bus_type' undeclared (first use in this function); did you mean 'pci_pcie_type'?
455 | bus_unregister_notifier(&pci_bus_type, &ctx->nb);
| ^~~~~~~~~~~~
| pci_pcie_type
cc1: some warnings being treated as errors
vim +193 drivers/power/sequencing/pwrseq-pcie-m2.c
179
180 static int pwrseq_m2_pcie_create_bt_node(struct pwrseq_pcie_m2_ctx *ctx,
181 struct device_node *parent)
182 {
183 struct device *dev = ctx->dev;
184 struct device_node *np;
185 int ret;
186
187 ctx->ocs = kzalloc_obj(*ctx->ocs);
188 if (!ctx->ocs)
189 return -ENOMEM;
190
191 of_changeset_init(ctx->ocs);
192
> 193 np = of_changeset_create_node(ctx->ocs, parent, "bluetooth");
194 if (!np) {
195 dev_err(dev, "Failed to create bluetooth node\n");
196 ret = -ENODEV;
197 goto err_destroy_changeset;
198 }
199
200 ret = of_changeset_add_prop_string(ctx->ocs, np, "compatible", "qcom,wcn7850-bt");
201 if (ret) {
202 dev_err(dev, "Failed to add bluetooth compatible: %d\n", ret);
203 goto err_destroy_changeset;
204 }
205
206 ret = of_changeset_apply(ctx->ocs);
207 if (ret) {
208 dev_err(dev, "Failed to apply changeset: %d\n", ret);
209 goto err_destroy_changeset;
210 }
211
212 ret = device_add_of_node(&ctx->serdev->dev, np);
213 if (ret) {
214 dev_err(dev, "Failed to add OF node: %d\n", ret);
215 goto err_revert_changeset;
216 }
217
218 return 0;
219
220 err_revert_changeset:
221 of_changeset_revert(ctx->ocs);
222 err_destroy_changeset:
223 of_changeset_destroy(ctx->ocs);
224 kfree(ctx->ocs);
225 ctx->ocs = NULL;
226
227 return ret;
228 }
229
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 3:49 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=202604031945.bEYKHUme-lkp@intel.com \
--to=lkp@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--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 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.