From: "Andy Yan" <andyshrk@163.com>
To: "Maud Spierings" <maud_spierings@murena.io>
Cc: Laurent.pinchart@ideasonboard.com, andrzej.hajda@intel.com,
andy.yan@rock-chips.com, devicetree@vger.kernel.org,
dmitry.baryshkov@oss.qualcomm.com,
dri-devel@lists.freedesktop.org, heiko@sntech.de,
jernej.skrabec@gmail.com, jonas@kwiboo.se, knaerzche@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
neil.armstrong@linaro.org, rfoss@kernel.org, simona@ffwll.ch,
tzimmermann@suse.de
Subject: Re:Re: [PATCH v8 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge library
Date: Fri, 17 Oct 2025 17:36:54 +0800 (CST) [thread overview]
Message-ID: <7d14fa88.9099.199f187848a.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <392dc6d7-a0e5-4f9e-85c4-8d811777a697@murena.io>
Hi Maud,
在 2025-10-17 17:19:21,"Maud Spierings" <maud_spierings@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@murena.io> wrote:
>>> Hi Andy,
>>>
>>>> From: Andy Yan <andy.yan@rock-chips.com>
>>>>
>>>> Add entry for Innosilicon hdmi bridge library
>>>>
>>>> Signed-off-by: Andy Yan <andy.yan@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@sholland.org>
>>>> S: Maintained
>>>> F: drivers/power/supply/ip5xxx_power.c
>>>>
>>>> +INNOSILICON HDMI BRIDGE DRIVER
>>>> +M: Andy Yan <andy.yan@rock-chips.com>
>>>> +L: dri-devel@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@suse.cz>
>>>> R: Amir Goldstein <amir73il@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
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-10-17 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 8:38 [PATCH v8 0/2] Convert inno hdmi to drm bridge Andy Yan
2025-10-16 8:38 ` [PATCH v8 1/2] drm/rockchip: inno-hdmi: Convert " Andy Yan
2025-10-20 12:45 ` Heiko Stuebner
2025-11-24 0:52 ` Andy Yan
2025-12-24 22:28 ` Dmitry Baryshkov
2025-10-16 8:38 ` [PATCH v8 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge library Andy Yan
2025-10-17 7:58 ` Maud Spierings
2025-10-17 8:56 ` Andy Yan
2025-10-17 9:19 ` Maud Spierings
2025-10-17 9:36 ` Andy Yan [this message]
2025-12-24 22:29 ` Dmitry Baryshkov
2025-12-24 22:32 ` [PATCH v8 0/2] Convert inno hdmi to drm bridge Dmitry Baryshkov
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=7d14fa88.9099.199f187848a.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maud_spierings@murena.io \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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