[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ff8b84c9-5bef-4cb9-a10b-b3bb1a017366@linaro.org>
Date: Fri, 5 Jul 2024 13:33:38 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Maxime Ripard <mripard@...nel.org>,
Alain Volmat <alain.volmat@...s.st.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Neil Armstrong <neil.armstrong@...aro.org>
Subject: Re: [PATCH] MAINTAINERS: drm/sti: mark it as Odd Fixes
On 05/07/2024 13:22, Maxime Ripard wrote:
> On Fri, Jul 05, 2024 at 01:19:50PM GMT, Daniel Vetter wrote:
>> On Fri, Jul 05, 2024 at 12:03:56PM +0200, Krzysztof Kozlowski wrote:
>>> Patches to STI DRM are not being picked up, so even though there is
>>> maintainer activity, it seems that these drivers are not being actively
>>> looked at. Reflect this in maintainer status.
>>
>> Note that since the driver is in drm-misc, other committers can also pick
>> up patches and push them. Both Neil and Dimtry have commit rights and
>> should be able to pick up your patches for you, if they get stuck.
>
> I've applied the patches.
>
> I don't think we should merge this one though, a one-off mishap can happen.
Sure.
Folks, maybe then pattern in maintainers should be somehow changed or grew?
The recommendation to all submitters is to use get_maintainers.pl. b4
also does it. In this particular case, using get_maintainers.pl or b4
will result in patches not being picked up.
Best regards,
Krzysztof
Powered by blists - more mailing lists