From: Jani Nikula <jani.nikula@linux.intel.com>
To: Christian Kujau <lists@nerdbynature.de>, intel-gfx@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm: bugs.freedesktop.org is no longer accepting bugs
Date: Mon, 17 Feb 2020 12:19:48 +0200 [thread overview]
Message-ID: <87y2t1v7ln.fsf@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.99999.375.2001141825300.21037@trent.utfs.org>
On Tue, 14 Jan 2020, Christian Kujau <lists@nerdbynature.de> wrote:
> Hello,
>
> this should apply cleanly to drm-tip.
>
>
> drm: bugs.freedesktop.org is no longer accepting bugs.
>
> freedesktop.org Bugzilla is no longer in use and new DRM bugs
> should be reported to https://gitlab.freedesktop.org/drm/intel
> instead. While we're at it, update some URLs of still-open bugs
> that have been moved to the new bug tracker.
>
> drivers/gpu/drm/i915/Kconfig | 3 +--
> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
> drivers/gpu/drm/i915/i915_utils.c | 2 +-
> drivers/gpu/drm/radeon/radeon_device.c | 2 +-
> 4 files changed, 4 insertions(+), 5 deletions(-)
>
> Signed-off-by: Christian Kujau <lists@nerdbynature.de>
Thanks for the patch, we've ended up fixing this with commits:
3a6a4f0810c8 ("MAINTAINERS: Update drm/i915 bug filing URL")
ddae4d7af0bb ("drm/i915: Update drm/i915 bug filing URL")
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-02-17 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 2:28 [Intel-gfx] [PATCH] drm: bugs.freedesktop.org is no longer accepting bugs Christian Kujau
2020-01-16 6:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-01-16 6:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-16 6:50 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-18 19:24 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2020-02-17 10:19 ` 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=87y2t1v7ln.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.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