From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Maxime Ripard <mripard@kernel.org>,
Alain Volmat <alain.volmat@foss.st.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: drm/sti: mark it as Odd Fixes
Date: Fri, 5 Jul 2024 13:33:38 +0200 [thread overview]
Message-ID: <ff8b84c9-5bef-4cb9-a10b-b3bb1a017366@linaro.org> (raw)
In-Reply-To: <20240705-hysterical-beluga-of-courtesy-38b2e2@houat>
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
next prev parent reply other threads:[~2024-07-05 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 10:03 Krzysztof Kozlowski
2024-07-05 11:19 ` Daniel Vetter
2024-07-05 11:22 ` Maxime Ripard
2024-07-05 11:33 ` Krzysztof Kozlowski [this message]
2024-07-05 13:41 ` Daniel Vetter
2024-07-05 15:14 ` Alain Volmat
2024-07-08 14:57 ` Maxime Ripard
2024-07-09 12:34 ` Alain Volmat
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=ff8b84c9-5bef-4cb9-a10b-b3bb1a017366@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=airlied@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--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
all inboxes | Powered by JetHome®