lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zof4Bp82iu7hZsSZ@phenom.ffwll.local>
Date: Fri, 5 Jul 2024 15:41:26 +0200
From: Daniel Vetter <daniel.vetter@...ll.ch>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: 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 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.
-Sima
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ