From: Moteen Shah <m-shah@ti.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: <devicetree@vger.kernel.org>, <robh@kernel.org>, <conor+dt@kernel.org>
Subject: Re: [PATCH v3 3/4] soc: ti: k3-socinfo: Export SoC registration helper
Date: Thu, 12 Nov 2026 14:02:56 +0530 [thread overview]
Message-ID: <a7959800-b60c-4f44-84eb-552c37dba376@ti.com> (raw)
In-Reply-To: <sashiko-outbox-210688@kernel.org>
On 12/11/26 13:49, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue to consider:
> - [High] soc: ti: k3-socinfo: missing header for k3_socinfo_register()
> breaks build
> --
>
> commit 50190b242a0586e1caa40c20a83d5610007110d5
> Author: Moteen Shah <m-shah@ti.com>
>
> soc: ti: k3-socinfo: Export SoC registration helper
>
> This commit splits the JTAG ID decoding and SoC device registration out of
> k3_chipinfo_probe() into an exported k3_socinfo_register() helper.
>
>> diff --git a/drivers/soc/ti/k3-socinfo.c b/drivers/soc/ti/k3-socinfo.c
>> index e21a2cd14c811..bf0829fb1d61c 100644
>> --- a/drivers/soc/ti/k3-socinfo.c
>> +++ b/drivers/soc/ti/k3-socinfo.c
>> @@ -5,6 +5,8 @@
>> * Copyright (C) 2020 Texas Instruments Incorporated - http://www.ti.com
>> */
>>
>> +#include <linux/device.h>
>> +#include <linux/export.h>
>> #include <linux/mfd/syscon.h>
>> #include <linux/nvmem-consumer.h>
>> #include <linux/of.h>
>> @@ -12,6 +14,7 @@
>> #include <linux/regmap.h>
>> #include <linux/platform_device.h>
>> #include <linux/slab.h>
>> +#include <linux/soc/ti/k3-socinfo.h>
> [Severity: High]
> Was include/linux/soc/ti/k3-socinfo.h omitted from this commit? Without
> that header declaring k3_socinfo_register(), compiling
> drivers/soc/ti/k3-socinfo.c fails with a missing header error.
Missed adding to the commit, I will send a new version for this.
Regards,
Moteen
next prev parent reply other threads:[~2026-11-12 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:10 [PATCH v3 0/4] soc: ti: Add TDA54 SCM configuration syscon support Moteen Shah
2026-11-12 8:10 ` [PATCH v3 1/4] dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf Moteen Shah
2026-11-12 8:23 ` sashiko-bot
2026-11-12 8:10 ` [PATCH v3 2/4] soc: ti: k3-socinfo: Use device managed allocations and unregistration Moteen Shah
2026-11-12 8:10 ` [PATCH v3 3/4] soc: ti: k3-socinfo: Export SoC registration helper Moteen Shah
2026-11-12 8:19 ` sashiko-bot
2026-11-12 8:32 ` Moteen Shah [this message]
2026-11-12 17:21 ` kernel test robot
2026-11-12 8:10 ` [PATCH v3 4/4] soc: ti: Add TDA54 SCM configuration syscon support Moteen Shah
2026-11-12 8:36 ` sashiko-bot
2026-11-12 16:16 ` 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=a7959800-b60c-4f44-84eb-552c37dba376@ti.com \
--to=m-shah@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@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