From: Vignesh Raman <vignesh.raman@collabora.com>
To: Eric Engestrom <eric@engestrom.ch>,
Helen Koike <helen.fornazier@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jonathan Corbet <corbet@lwn.net>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/doc: recommend forking drm/kernel rather than uploading a distinct copy
Date: Fri, 20 Feb 2026 11:08:45 +0530 [thread overview]
Message-ID: <b7f86ada-a74d-4fb2-83d2-5b4ef18e00c4@collabora.com> (raw)
In-Reply-To: <20260219135645.261192-1-eric@engestrom.ch>
Hi Eric,
On 19/02/26 19:26, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <eric@engestrom.ch>
> ---
> Documentation/gpu/automated_testing.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git ./Documentation/gpu/automated_testing.rst ./Documentation/gpu/automated_testing.rst
> index 62aa3ede02a5df3f590b..8a7328aef10ef39ee329 100644
> --- ./Documentation/gpu/automated_testing.rst
> +++ ./Documentation/gpu/automated_testing.rst
> @@ -99,7 +99,8 @@ How to enable automated testing on your tree
> ============================================
>
> 1. Create a Linux tree in https://gitlab.freedesktop.org/ if you don't have one
> -yet
> +yet, by forking https://gitlab.freedesktop.org/drm/kernel (this allows GitLab
> +to internally track that these are the same git objects).
Reviewed-by: Vignesh Raman <vignesh.raman@collabora.com>
Regards,
Vignesh
>
> 2. In your kernel repo's configuration (eg.
> https://gitlab.freedesktop.org/janedoe/linux/-/settings/ci_cd), change the
next prev parent reply other threads:[~2026-02-20 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 13:56 [PATCH] drm/doc: recommend forking drm/kernel rather than uploading a distinct copy Eric Engestrom
2026-02-20 5:38 ` Vignesh Raman [this message]
2026-06-17 10:26 ` Vignesh Raman
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=b7f86ada-a74d-4fb2-83d2-5b4ef18e00c4@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@engestrom.ch \
--cc=helen.fornazier@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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