All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915/guc: Remove stale comment for	q_fail
Date: Wed, 24 May 2017 15:33:54 +0300	[thread overview]
Message-ID: <87zie2sabx.fsf@intel.com> (raw)
In-Reply-To: <20170518113104.54400-1-michal.wajdeczko@intel.com>

On Thu, 18 May 2017, Michal Wajdeczko <michal.wajdeczko@intel.com> wrote:
> This member was dropped long time ago.
>
> Fixes: 774439e1 ("drm/i915/guc: re-optimise i915_guc_client layout")

For future reference, please only use Fixes: to indicate actual bugs
fixed. I use the tag to track fixes that need to be backported, stale
comments or typo fixes or whatnot need not, and excessive Fixes: use
leads to noise for me. That said, when in doubt, err on the side of
adding one.

Thanks,
Jani.


> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_uc.h | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uc.h b/drivers/gpu/drm/i915/intel_uc.h
> index 7618b71..8d52a37 100644
> --- a/drivers/gpu/drm/i915/intel_uc.h
> +++ b/drivers/gpu/drm/i915/intel_uc.h
> @@ -59,8 +59,6 @@ struct drm_i915_gem_request;
>   *                available in the work queue (note, the queue is shared,
>   *                not per-engine). It is OK for this to be nonzero, but
>   *                it should not be huge!
> - *   q_fail: failed to enqueue a work item. This should never happen,
> - *           because we check for space beforehand.
>   *   b_fail: failed to ring the doorbell. This should never happen, unless
>   *           somehow the hardware misbehaves, or maybe if the GuC firmware
>   *           crashes? We probably need to reset the GPU to recover.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-05-24 12:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 11:31 [PATCH 1/3] drm/i915/guc: Remove stale comment for q_fail Michal Wajdeczko
2017-05-18 11:31 ` [PATCH 2/3] drm/i915/guc: Remove failed doorbell stat from debugfs Michal Wajdeczko
2017-05-18 11:31 ` [PATCH 3/3] drm/i915/guc: Remove last submission result " Michal Wajdeczko
2017-05-19  8:30   ` Chris Wilson
2017-05-19  8:38   ` Joonas Lahtinen
2017-05-19  8:55     ` Michal Wajdeczko
2017-05-18 16:38 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] drm/i915/guc: Remove stale comment for q_fail Patchwork
2017-05-18 17:12   ` Michal Wajdeczko
2017-05-19 10:28     ` Chris Wilson
2017-05-24 12:33 ` 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=87zie2sabx.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@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 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.