Hello Emil,
On Thu, Jun 18, 2015 at 03:51:26PM +0100, Emil Velikov wrote:
> > I had planned to send a second pull request for 4.2 with some
> > additional hdcp patches that depend on scm changes coming in via
> > arm-soc tree for 4.2.. if that is ok, I can include this patch with
> > that second pull req.. otherwise I'm ok with Dave applying it
> > directly or you taking it in via gpio tree. Either way is fine by me.
> >
> Mildly related:
>
> Rob, would it make things a bit easier if we have you listed in
> MAINTAINERS for the msm/freedreno driver ?
>
> Uwe, you might have greater input if you explicitly CC the
> {unofficial,} maintainer of the relevant driver. Some drivers don't
> have one explicitly listed in MAINTAINERS, so git log tends to help
> there :-)
I consider it hard to choose the right set of recipents for areas where
I don't usually patch. Addressing too much people is bad as is addressing
too less. And what is considered right differs per
subsystem/maintainer/contributor. I don't claim it's impossible to find
out the right person, but for a patch stack with more than say a dozen
patches distributed all over the source tree it's the easiest to check
scripts/get_maintainer.pl and select what looks reasonable from its
output. So having the maintainer listed is definitly nice because at
least for me it increases the chance considerably to pick him for cc.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
