From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Martin Peres <martin.peres@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Update bug URL to point at gitlab issues
Date: Mon, 02 Dec 2019 12:30:22 +0200 [thread overview]
Message-ID: <878snvkojl.fsf@intel.com> (raw)
In-Reply-To: <20191125104248.1690891-1-chris@chris-wilson.co.uk>
On Mon, 25 Nov 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> We are moving our issue tracking over from bugs.fd.o to gitlab.fd.o, so
> update the user instructions accordingly.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
> drivers/gpu/drm/i915/i915_utils.c | 3 +--
> drivers/gpu/drm/i915/i915_utils.h | 2 ++
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 2b30a45fa25c..1cf53fd4fe66 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1817,7 +1817,7 @@ void i915_capture_error_state(struct drm_i915_private *i915,
> if (!xchg(&warned, true) &&
> ktime_get_real_seconds() - DRIVER_TIMESTAMP < DAY_AS_SECONDS(180)) {
> pr_info("GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.\n");
> - pr_info("Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel\n");
> + pr_info("Please file a _new_ bug report on " FDO_BUG_URL "\n");
> pr_info("drm/i915 developers can then reassign to the right component if it's not a kernel issue.\n");
> pr_info("The GPU crash dump is required to analyze GPU hangs, so please always attach it.\n");
> pr_info("GPU crash dump saved to /sys/class/drm/card%d/error\n",
> diff --git a/drivers/gpu/drm/i915/i915_utils.c b/drivers/gpu/drm/i915/i915_utils.c
> index c47261ae86ea..9b68b21becf1 100644
> --- a/drivers/gpu/drm/i915/i915_utils.c
> +++ b/drivers/gpu/drm/i915/i915_utils.c
> @@ -8,8 +8,7 @@
> #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 " \
> +#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL \
> "providing the dmesg log by booting with drm.debug=0xf"
Space between URL and "providing"?
>
> void
> diff --git a/drivers/gpu/drm/i915/i915_utils.h b/drivers/gpu/drm/i915/i915_utils.h
> index 04139ba1191e..13674b016092 100644
> --- a/drivers/gpu/drm/i915/i915_utils.h
> +++ b/drivers/gpu/drm/i915/i915_utils.h
> @@ -34,6 +34,8 @@
> struct drm_i915_private;
> struct timer_list;
>
> +#define FDO_BUG_URL "https://gitlab.freedesktop.org/drm/intel/issues/new?"
Do we really need the question mark?
BR,
Jani.
> +
> #undef WARN_ON
> /* Many gcc seem to no see through this and fall over :( */
> #if 0
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Update bug URL to point at gitlab issues
Date: Mon, 02 Dec 2019 12:30:22 +0200 [thread overview]
Message-ID: <878snvkojl.fsf@intel.com> (raw)
Message-ID: <20191202103022.9qYNRUXvZmLuwE0JPqkGKB17NFfsW6IVGtuZQfs9c7k@z> (raw)
In-Reply-To: <20191125104248.1690891-1-chris@chris-wilson.co.uk>
On Mon, 25 Nov 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> We are moving our issue tracking over from bugs.fd.o to gitlab.fd.o, so
> update the user instructions accordingly.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
> drivers/gpu/drm/i915/i915_utils.c | 3 +--
> drivers/gpu/drm/i915/i915_utils.h | 2 ++
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 2b30a45fa25c..1cf53fd4fe66 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1817,7 +1817,7 @@ void i915_capture_error_state(struct drm_i915_private *i915,
> if (!xchg(&warned, true) &&
> ktime_get_real_seconds() - DRIVER_TIMESTAMP < DAY_AS_SECONDS(180)) {
> pr_info("GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.\n");
> - pr_info("Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel\n");
> + pr_info("Please file a _new_ bug report on " FDO_BUG_URL "\n");
> pr_info("drm/i915 developers can then reassign to the right component if it's not a kernel issue.\n");
> pr_info("The GPU crash dump is required to analyze GPU hangs, so please always attach it.\n");
> pr_info("GPU crash dump saved to /sys/class/drm/card%d/error\n",
> diff --git a/drivers/gpu/drm/i915/i915_utils.c b/drivers/gpu/drm/i915/i915_utils.c
> index c47261ae86ea..9b68b21becf1 100644
> --- a/drivers/gpu/drm/i915/i915_utils.c
> +++ b/drivers/gpu/drm/i915/i915_utils.c
> @@ -8,8 +8,7 @@
> #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 " \
> +#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL \
> "providing the dmesg log by booting with drm.debug=0xf"
Space between URL and "providing"?
>
> void
> diff --git a/drivers/gpu/drm/i915/i915_utils.h b/drivers/gpu/drm/i915/i915_utils.h
> index 04139ba1191e..13674b016092 100644
> --- a/drivers/gpu/drm/i915/i915_utils.h
> +++ b/drivers/gpu/drm/i915/i915_utils.h
> @@ -34,6 +34,8 @@
> struct drm_i915_private;
> struct timer_list;
>
> +#define FDO_BUG_URL "https://gitlab.freedesktop.org/drm/intel/issues/new?"
Do we really need the question mark?
BR,
Jani.
> +
> #undef WARN_ON
> /* Many gcc seem to no see through this and fall over :( */
> #if 0
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Martin Peres <martin.peres@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Update bug URL to point at gitlab issues
Date: Mon, 02 Dec 2019 12:30:22 +0200 [thread overview]
Message-ID: <878snvkojl.fsf@intel.com> (raw)
In-Reply-To: <20191125104248.1690891-1-chris@chris-wilson.co.uk>
On Mon, 25 Nov 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> We are moving our issue tracking over from bugs.fd.o to gitlab.fd.o, so
> update the user instructions accordingly.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
> drivers/gpu/drm/i915/i915_utils.c | 3 +--
> drivers/gpu/drm/i915/i915_utils.h | 2 ++
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 2b30a45fa25c..1cf53fd4fe66 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1817,7 +1817,7 @@ void i915_capture_error_state(struct drm_i915_private *i915,
> if (!xchg(&warned, true) &&
> ktime_get_real_seconds() - DRIVER_TIMESTAMP < DAY_AS_SECONDS(180)) {
> pr_info("GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.\n");
> - pr_info("Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel\n");
> + pr_info("Please file a _new_ bug report on " FDO_BUG_URL "\n");
> pr_info("drm/i915 developers can then reassign to the right component if it's not a kernel issue.\n");
> pr_info("The GPU crash dump is required to analyze GPU hangs, so please always attach it.\n");
> pr_info("GPU crash dump saved to /sys/class/drm/card%d/error\n",
> diff --git a/drivers/gpu/drm/i915/i915_utils.c b/drivers/gpu/drm/i915/i915_utils.c
> index c47261ae86ea..9b68b21becf1 100644
> --- a/drivers/gpu/drm/i915/i915_utils.c
> +++ b/drivers/gpu/drm/i915/i915_utils.c
> @@ -8,8 +8,7 @@
> #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 " \
> +#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL \
> "providing the dmesg log by booting with drm.debug=0xf"
Space between URL and "providing"?
>
> void
> diff --git a/drivers/gpu/drm/i915/i915_utils.h b/drivers/gpu/drm/i915/i915_utils.h
> index 04139ba1191e..13674b016092 100644
> --- a/drivers/gpu/drm/i915/i915_utils.h
> +++ b/drivers/gpu/drm/i915/i915_utils.h
> @@ -34,6 +34,8 @@
> struct drm_i915_private;
> struct timer_list;
>
> +#define FDO_BUG_URL "https://gitlab.freedesktop.org/drm/intel/issues/new?"
Do we really need the question mark?
BR,
Jani.
> +
> #undef WARN_ON
> /* Many gcc seem to no see through this and fall over :( */
> #if 0
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-12-02 10:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 10:42 [PATCH] drm/i915: Update bug URL to point at gitlab issues Chris Wilson
2019-11-25 10:42 ` [Intel-gfx] " Chris Wilson
2019-11-25 12:51 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-11-25 12:51 ` [Intel-gfx] " Patchwork
2019-12-02 10:30 ` Jani Nikula [this message]
2019-12-02 10:30 ` [PATCH] " Jani Nikula
2019-12-02 10:30 ` [Intel-gfx] " Jani Nikula
2019-12-02 11:26 ` Peres, Martin
2019-12-02 11:26 ` [Intel-gfx] " Peres, Martin
2019-12-02 11:36 ` Jani Nikula
2019-12-02 11:36 ` Jani Nikula
2019-12-02 11:36 ` [Intel-gfx] " Jani Nikula
2019-12-02 14:25 ` Chris Wilson
2019-12-02 14:25 ` [Intel-gfx] " Chris Wilson
2019-12-02 16:45 ` Peres, Martin
2019-12-02 16:45 ` Peres, Martin
2019-12-02 16:45 ` [Intel-gfx] " Peres, Martin
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=878snvkojl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=martin.peres@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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.