From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] MAINTAINERS: drop dri-devel list for i915
Date: Sat, 29 Oct 2016 15:46:14 +0300 [thread overview]
Message-ID: <87insbmig9.fsf@intel.com> (raw)
In-Reply-To: <1477498292-9808-1-git-send-email-jani.nikula@intel.com>
On Wed, 26 Oct 2016, Jani Nikula <jani.nikula@intel.com> wrote:
> In practice, none of the i915 developers Cc dri-devel for strictly i915
> specific patches. Make MAINTAINERS reflect reality, and reduce random
> i915 specific noise on dri-devel.
>
> Also, we have a fairly large crowd reading and responding on intel-gfx,
> and we're pretty good at involving dri-devel when that is appropriate.
>
> Cc: dri-devel@lists.freedesktop.org
> Acked-by: Daniel Vetter <daniel@ffwll.ch>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Pushed.
BR,
Jani.
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e60e0a188229..f3547144e743 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4054,7 +4054,6 @@ INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets)
> M: Daniel Vetter <daniel.vetter@intel.com>
> M: Jani Nikula <jani.nikula@linux.intel.com>
> L: intel-gfx@lists.freedesktop.org
> -L: dri-devel@lists.freedesktop.org
> W: https://01.org/linuxgraphics/
> Q: http://patchwork.freedesktop.org/project/intel-gfx/
> T: git git://anongit.freedesktop.org/drm-intel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-10-29 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 16:11 [PATCH] MAINTAINERS: drop dri-devel list for i915 Jani Nikula
2016-10-29 12:46 ` Jani Nikula [this message]
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=87insbmig9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).