[PATCH v8 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge library

[Andy Yan]

Hi Maud，

在 2025-10-17 17:19:21，"Maud Spierings" <maud_spierings at murena.io> 写道：
>Hi Andy,
>
>On 10/17/25 10:56, Andy Yan wrote:
>>
>> Hello Maud，
>>
>> At 2025-10-17 15:58:22, "Maud Spierings" <maud_spierings at murena.io> wrote:
>>> Hi Andy,
>>>
>>>> From: Andy Yan <andy.yan at rock-chips.com>
>>>>
>>>> Add entry for Innosilicon hdmi bridge library
>>>>
>>>> Signed-off-by: Andy Yan <andy.yan at rock-chips.com>
>>>> ---
>>>>
>>>> (no changes since v1)
>>>>
>>>>   MAINTAINERS | 8 ++++++++
>>>>   1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index f9f985c7d7479..0adcfb1c264a1 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -12299,6 +12299,14 @@ M:	Samuel Holland <samuel at sholland.org>
>>>>   S:	Maintained
>>>>   F:	drivers/power/supply/ip5xxx_power.c
>>>>   
>>>> +INNOSILICON HDMI BRIDGE DRIVER
>>>> +M:	Andy Yan <andy.yan at rock-chips.com>
>>>> +L:	dri-devel at lists.freedesktop.org
>>>> +S:	Maintained
>>>> +T:	git https://gitlab.freedesktop.org/drm/misc/kernel.git
>>>> +F:	drivers/gpu/drm/bridge/inno-hdmi.c
>>>> +F:	include/drm/bridge/inno_hdmi.h
>>>> +
>>>>   INOTIFY
>>>>   M:	Jan Kara <jack at suse.cz>
>>>>   R:	Amir Goldstein <amir73il at gmail.com>
>>>> -- 
>>>> 2.43.0
>>> I believe this patch should be squashed into the patch that actually
>>> creates the files listed in the MAINTAINERS entry, like I do here [1].
>>> Checkpatch should be complaining about patch [1/2] if I'm not mistaken,
>>> when you run `b4 prep --check`.
>> We talked about something similar here[2]：
>> Maxime believes they should be separate patches,
>> And I've seen many merged commits in the kernel are also handle MAINTAINERS entry as separate patches
>>
>>
>> [2]https://lore.kernel.org/linux-rockchip/3ygqnj4idey7u4m7ltlv7pnfhkkvcepmpfdijdszctaeopq3ky@qteg33comjl3/
>
>It seems there are indeed opinions about this [3], guess whatever the 
>actual maintainer wants is what will happen, sorry to disturb.

It's okay, I don't have a strong preference for either approach. It ultimately depends on the maintainer's decision

>
>
>Would be nice to get some central guideline about how it should be.
>
>
>[3] 
>https://lore.kernel.org/all/51b72003-e9a5-4f34-ad08-249fc24b3041@kernel.org/
>
>>
>>> Link:
>>> https://lore.kernel.org/all/20251009-max25014-v4-1-6adb2a0aa35f@gocontroll.com/
>>> [1]
>>>
>>> Kind regards,
>>> Maud