On Tue, 26 Apr 2016, Daniel Vetter <[email protected]> wrote: > New props need to be cc'ed to dri-devel. And we need to coordinate with > other folks doing the same and have one unified set of blending ops.
The more general answer is, check the maintainers for the files you're changing, in the MAINTAINERS file. scripts/get_maintainer.pl will help you with that. $ scripts/get_maintainer.pl 0001-drm-Introduce-the-blend-func-property.patch Jonathan Corbet <[email protected]> (maintainer:DOCUMENTATION) David Airlie <[email protected]> (maintainer:DRM DRIVERS) Daniel Vetter <[email protected]> (commit_signer:45/42=100%,authored:19/42=45%) Lukas Wunner <[email protected]> (commit_signer:8/42=19%,authored:7/42=17%) Thierry Reding <[email protected]> (commit_signer:7/42=17%) Darren Hart <[email protected]> (commit_signer:3/42=7%) Jani Nikula <[email protected]> (commit_signer:3/42=7%,authored:3/42=7%) [email protected] (open list:DOCUMENTATION) [email protected] (open list) [email protected] (open list:DRM DRIVERS) You can often ignore the "commit_signer" stats (and sometimes people get annyoed for being randomly Cc'd for things they did long ago), and here you need to take into account the following patches and include the drm/i915 list and maintainers. get_maintainer.pl is not the silver bullet, but it will give you an idea, and in this case a clear indication intel-gfx is not enough. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
