mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alain Volmat <alain.volmat@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Maxime Ripard <mripard@kernel.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	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>
Cc: Philippe CORNU <philippe.cornu@foss.st.com>,
	Yannick FERTRE <yannick.fertre@foss.st.com>,
	Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
Subject: Re: [PATCH] MAINTAINERS: drm/sti: mark it as Odd Fixes
Date: Fri, 5 Jul 2024 17:14:36 +0200	[thread overview]
Message-ID: <20240705151436.GA3949471@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <Zof4Bp82iu7hZsSZ@phenom.ffwll.local>

Hi Krzysztof, Daniel, and Maxime,

On Fri, Jul 05, 2024 at 03:41:26PM +0200, Daniel Vetter wrote:
> On Fri, Jul 05, 2024 at 01:33:38PM +0200, Krzysztof Kozlowski wrote:
> > 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.
> 
> I think get_maintainers.pl is correct: You get the driver maintainer, plus
> drm-misc maintainers as official fallback, plus Dave&me as fallback of
> last resorts. So all correct.
> 
> What's special with the commit rights model is that other committers that
> work all over the subsystem can also pick up the patches for you, so that
> the drm-misc mainters don't become a bottleneck. But the ideal person
> there are drm-misc committers who work in your team or company, or someone
> else where you have some goodwill credits to spend with and ask them for a
> favour. And there's just no way to model that and make sure the script
> gives you the right suggestions.

Many thanks for all your emails and your support.

In the past, I've never committed patches to drm-misc myself and, to be honest,
missed the point that as a drm driver maintainer, I should also do so.
Thanks to recent discussions, I now fully understand how it should be done.

That said, since the volume of drm/sti patches is rather small,
I will from now on request help for commit from drm/stm (Philippe, Yannick, and Raphael)
and drm-misc maintainers in a more "pro-active" way :-)

Sorry for the inconvenience, and once again, many thanks for your support.

Alain


> -Sima
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

  reply	other threads:[~2024-07-05 15:15 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
2024-07-05 13:41       ` Daniel Vetter
2024-07-05 15:14         ` Alain Volmat [this message]
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=20240705151436.GA3949471@gnbcxd0016.gnb.st.com \
    --to=alain.volmat@foss.st.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=philippe.cornu@foss.st.com \
    --cc=raphael.gallais-pou@foss.st.com \
    --cc=tzimmermann@suse.de \
    --cc=yannick.fertre@foss.st.com \
    /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®