intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] dim: Triple-check and tripe warning when merging patches that touch files outside i915.
Date: Fri, 13 Jan 2017 09:04:12 +0200	[thread overview]
Message-ID: <87d1frfnkj.fsf@intel.com> (raw)
In-Reply-To: <1484262333-22025-1-git-send-email-rodrigo.vivi@intel.com>

On Fri, 13 Jan 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> Most of commiters already knows that by heart and also dim already
> have this warning. So maybe this is just Bart writing to blackboard. Duh!
>
> Anyway for my own usage this tripe check will help for sure.
> Maybe it help someone else in the future.

Well, this has changed with drm-misc; very few of the commits there have
acks from Dave. And that was sort of the point in that tree, to scale
better and not depend on his acks on every little detail.

I suppose the checks in dim could be branch specific.

BR,
Jani.


>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  dim           | 4 ++++
>  drm-intel.rst | 4 +++-
>  2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/dim b/dim
> index eec5e43..73f6212 100755
> --- a/dim
> +++ b/dim
> @@ -933,6 +933,10 @@ function checkpatch_commit
>  			echo -e "The following files are outside of i915 maintenance scope:\n"
>  			echo "$non_i915_files"
>  			echo -e "\nConfirm you have appropriate Acked-by and Reviewed-by for above files."
> +			local acked_by_airlie=$($cmd | grep "Acked-by: Dave Airlie <airlied@redhat.com>")
> +			if [ "$acked_by_airlie" == "" ]; then
> +			    echo -e "\nRemind that for drm you should have an Acked-by from Dave Airlie <airlied@redhat.com>"
> +			fi
>  		fi
>  	fi
>  }
> diff --git a/drm-intel.rst b/drm-intel.rst
> index 79db1cf..583a687 100644
> --- a/drm-intel.rst
> +++ b/drm-intel.rst
> @@ -300,7 +300,9 @@ the right decisions, and for others to set their the expectations right.
>  
>  The short list:
>  
> -* Only push patches changing `drivers/gpu/drm/i915`.
> +* Only push patches changing `drivers/gpu/drm/i915`. If dim mentioned that you
> +  are touching files outside i915 stop and make sure that you have the proper
> +  Acked-by. Specially for drm files an Acked-by from Dave Airlie is required.
>  
>  * Only push patches to `drm-intel-next-queued` branch.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-01-13  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 23:05 [PATCH] dim: Triple-check and tripe warning when merging patches that touch files outside i915 Rodrigo Vivi
2017-01-13  7:04 ` Jani Nikula [this message]
2017-01-13 18:38   ` Rodrigo Vivi
2017-01-23 16:44   ` Daniel Vetter

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=87d1frfnkj.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.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;
as well as URLs for NNTP newsgroup(s).