Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ryszard Knop <ryszard.knop@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] MAINTAINERS: Move the drm-intel repo location to fd.o GitLab
Date: Wed, 24 Apr 2024 15:45:34 +0300	[thread overview]
Message-ID: <871q6vq68h.fsf@intel.com> (raw)
In-Reply-To: <20240424114159.38719-1-ryszard.knop@intel.com>

On Wed, 24 Apr 2024, Ryszard Knop <ryszard.knop@intel.com> wrote:
> The drm-intel repo is moving from the classic fd.o git host to GitLab.
> Update its location with a URL matching other fd.o GitLab kernel trees.
>
> Signed-off-by: Ryszard Knop <ryszard.knop@intel.com>

Acked-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d6327dc12cb1..fbf7371a0bb0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10854,7 +10854,7 @@ W:	https://drm.pages.freedesktop.org/intel-docs/
>  Q:	http://patchwork.freedesktop.org/project/intel-gfx/
>  B:	https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
>  C:	irc://irc.oftc.net/intel-gfx
> -T:	git git://anongit.freedesktop.org/drm-intel
> +T:	git https://gitlab.freedesktop.org/drm/i915/kernel.git
>  F:	Documentation/ABI/testing/sysfs-driver-intel-i915-hwmon
>  F:	Documentation/gpu/i915.rst
>  F:	drivers/gpu/drm/ci/xfails/i915*

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2024-04-24 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 11:41 [PATCH] MAINTAINERS: Move the drm-intel repo location to fd.o GitLab Ryszard Knop
2024-04-24 12:16 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-04-24 12:45 ` Jani Nikula [this message]
2024-04-26 15:47 ` [PATCH] " Lucas De Marchi
2024-04-26 16:02   ` Tvrtko Ursulin
2024-04-29 12:35     ` Rodrigo Vivi

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=871q6vq68h.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ryszard.knop@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