From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
matthias.bgg@kernel.org, nancy.lin@mediatek.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: mediatek: Add deprecated compatible to mmsys
Date: Fri, 11 Nov 2022 09:31:15 +0100 [thread overview]
Message-ID: <465810f6-98f0-4125-179d-dd484e5ac09d@gmail.com> (raw)
In-Reply-To: <eae90e1e-408b-4f9a-9211-649da28b0358@collabora.com>
On 10/11/2022 16:03, AngeloGioacchino Del Regno wrote:
> Il 10/11/22 13:02, matthias.bgg@kernel.org ha scritto:
>> From: Matthias Brugger <matthias.bgg@gmail.com>
>>
>> For backward compatibility we add the deprecated compatible.
>>
>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>
> Hello Matthias,
>
> You forgot to advertise that this commit depends on [1]... and I'm afraid
> that you have to push a v2 anyway, because...
>
Well yes I based it against mediateks for-next branch, sorry for the confusion.
>> ---
>> drivers/soc/mediatek/mtk-mmsys.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/soc/mediatek/mtk-mmsys.c b/drivers/soc/mediatek/mtk-mmsys.c
>> index ba2e79b26993b..47106f557c574 100644
>> --- a/drivers/soc/mediatek/mtk-mmsys.c
>> +++ b/drivers/soc/mediatek/mtk-mmsys.c
>> @@ -303,6 +303,10 @@ static const struct of_device_id of_match_mtk_mmsys[] = {
>> .compatible = "mediatek,mt8192-mmsys",
>> .data = &mt8192_mmsys_driver_data,
>> },
>> + { /* deprecated compatible */
>> + .compatible = "mediatek,mt8195-mmsys",
>> + .data = &mt8195_mmsys_match_data,
>
> ...mt8195_mmsys_match_data doesn't exist anymore after [1], so this should be
>
> .data = &mt8195_vdosys0_driver_data,
>
Of course, should have compile tested at least. /o\
Regards,
Matthias
> [1]: https://patchwork.kernel.org/project/linux-mediatek/list/?series=681097
>
> Cheers,
> Angelo
>
prev parent reply other threads:[~2022-11-11 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 12:02 matthias.bgg
2022-11-10 15:03 ` AngeloGioacchino Del Regno
2022-11-11 8:31 ` Matthias Brugger [this message]
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=465810f6-98f0-4125-179d-dd484e5ac09d@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@kernel.org \
--cc=nancy.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®