From: Martin Peres <martin.peres@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 1/2] drm/i915: update the bug-filing instructions link
Date: Thu, 12 Dec 2019 14:51:50 +0200 [thread overview]
Message-ID: <20191212125151.118946-1-martin.peres@linux.intel.com> (raw)
Freedesktop's Bugzilla instance is no more, and bugs have been migrated
to gitlab.freedesktop.org/drm/intel.
The instructions also moved from 01.org to fd.o's gitlab to make it
easier to keep up to date.
This patch updates the link presented to the user after a GPU hang.
Signed-off-by: Martin Peres <martin.peres@linux.intel.com>
---
drivers/gpu/drm/i915/i915_utils.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_utils.c b/drivers/gpu/drm/i915/i915_utils.c
index c47261ae86ea..7b899259bfbb 100644
--- a/drivers/gpu/drm/i915/i915_utils.c
+++ b/drivers/gpu/drm/i915/i915_utils.c
@@ -8,9 +8,8 @@
#include "i915_drv.h"
#include "i915_utils.h"
-#define FDO_BUG_URL "https://bugs.freedesktop.org/enter_bug.cgi?product=DRI"
-#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL " against DRM/Intel " \
- "providing the dmesg log by booting with drm.debug=0xf"
+#define FDO_BUG_URL "https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs"
+#define FDO_BUG_MSG "Please file a bug according to " FDO_BUG_URL "."
void
__i915_printk(struct drm_i915_private *dev_priv, const char *level,
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-12-12 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 12:51 Martin Peres [this message]
2019-12-12 12:51 ` [Intel-gfx] [PATCH 2/2] MAINTAINERS: update the i915 bug filing instruction Martin Peres
2019-12-12 18:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: update the bug-filing instructions link Patchwork
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=20191212125151.118946-1-martin.peres@linux.intel.com \
--to=martin.peres@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.