From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Daniel Golle <daniel@makrotopia.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
William-tw Lin <william-tw.lin@mediatek.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] soc: mediatek: mtk-socinfo: depends on CONFIG_SOC_BUS
Date: Tue, 20 Feb 2024 09:56:05 +0100 [thread overview]
Message-ID: <f1fc67d4-f979-4c3e-988f-a803b7b11c46@collabora.com> (raw)
In-Reply-To: <CAGXv+5EKCrvsvZwc2zYiMWAeT9vqvU0JnDrz=WBoebBBbcgp0g@mail.gmail.com>
Il 20/02/24 07:40, Chen-Yu Tsai ha scritto:
> On Thu, Feb 8, 2024 at 1:43 AM Daniel Golle <daniel@makrotopia.org> wrote:
>>
>> The mtk-socinfo driver uses symbols 'soc_device_register' and
>> 'soc_device_unregister' which are part of the bus driver for
>> System-on-Chip devices.
>>
>> Select SOC_BUS to make sure that driver is built and the symbols are
>> available.
>>
>> Fixes: 423a54da3c7e ("soc: mediatek: mtk-socinfo: Add driver for getting chip information")
>> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
>
> Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
>
> Angelo, I believe this should be picked up for -next?
>
I'll pick this up for fixes, as I've already sent the PRs for v6.9.
> Also, mediatek/v6.8-next/soc is missing from mediatek/for-next in today's
> linux-next.
>
Fixing immediately.
>> ---
>> drivers/soc/mediatek/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/soc/mediatek/Kconfig b/drivers/soc/mediatek/Kconfig
>> index 50c664b65f4d4..1b7afb19ccd63 100644
>> --- a/drivers/soc/mediatek/Kconfig
>> +++ b/drivers/soc/mediatek/Kconfig
>> @@ -72,6 +72,7 @@ config MTK_SOCINFO
>> tristate "MediaTek SoC Information"
>> default y
>> depends on NVMEM_MTK_EFUSE
>> + select SOC_BUS
>> help
>> The MediaTek SoC Information (mtk-socinfo) driver provides
>> information about the SoC to the userspace including the
>> --
>> 2.43.0
>>
>>
next prev parent reply other threads:[~2024-02-20 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 17:42 Daniel Golle
2024-02-20 6:40 ` Chen-Yu Tsai
2024-02-20 8:56 ` AngeloGioacchino Del Regno [this message]
2024-02-20 9:03 ` Chen-Yu Tsai
2024-02-20 9:03 ` AngeloGioacchino Del Regno
2024-02-20 8:59 ` Matthias Brugger
2024-04-09 12:06 ` AngeloGioacchino Del Regno
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=f1fc67d4-f979-4c3e-988f-a803b7b11c46@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=wenst@chromium.org \
--cc=william-tw.lin@mediatek.com \
/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
all inboxes | Powered by JetHome®