[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <392dc6d7-a0e5-4f9e-85c4-8d811777a697@murena.io>
Date: Fri, 17 Oct 2025 11:19:21 +0200
From: Maud Spierings <maud_spierings@...ena.io>
To: Andy Yan <andyshrk@....com>
Cc: Laurent.pinchart@...asonboard.com, andrzej.hajda@...el.com,
andy.yan@...k-chips.com, devicetree@...r.kernel.org,
dmitry.baryshkov@....qualcomm.com, dri-devel@...ts.freedesktop.org,
heiko@...ech.de, jernej.skrabec@...il.com, jonas@...boo.se,
knaerzche@...il.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
neil.armstrong@...aro.org, rfoss@...nel.org, simona@...ll.ch,
tzimmermann@...e.de
Subject: Re: [PATCH v8 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge
library
Hi Andy,
On 10/17/25 10:56, Andy Yan wrote:
>
> Hello Maud,
>
> At 2025-10-17 15:58:22, "Maud Spierings" <maud_spierings@...ena.io> wrote:
>> Hi Andy,
>>
>>> From: Andy Yan <andy.yan@...k-chips.com>
>>>
>>> Add entry for Innosilicon hdmi bridge library
>>>
>>> Signed-off-by: Andy Yan <andy.yan@...k-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@...lland.org>
>>> S: Maintained
>>> F: drivers/power/supply/ip5xxx_power.c
>>>
>>> +INNOSILICON HDMI BRIDGE DRIVER
>>> +M: Andy Yan <andy.yan@...k-chips.com>
>>> +L: dri-devel@...ts.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@...e.cz>
>>> R: Amir Goldstein <amir73il@...il.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.
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
Powered by blists - more mailing lists