All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oscar Mateo <oscar.mateo@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 4/5] drm/i915: Create a new category of display WAs
Date: Tue, 13 Feb 2018 13:34:44 -0800	[thread overview]
Message-ID: <3114cf07-1551-6c58-62c7-3921d91287ae@intel.com> (raw)
In-Reply-To: <151855503767.25823.16433581918202475691@mail.alporthouse.com>



On 2/13/2018 12:50 PM, Chris Wilson wrote:
> Quoting Jani Nikula (2018-02-13 20:02:55)
>> On Tue, 13 Feb 2018, Oscar Mateo <oscar.mateo@intel.com> wrote:
>>> @@ -8979,6 +8701,7 @@ static void i830_init_clock_gating(struct drm_i915_private *dev_priv)
>>>   void intel_init_clock_gating(struct drm_i915_private *dev_priv)
>>>   {
>>>        dev_priv->display.init_clock_gating(dev_priv);
>>> +     intel_disp_workarounds_apply(dev_priv);
>> Please don't abbreviate display to disp, use the full word instead,
>> throughout the series. Rationale:
> And in general, use the full name for global functions and data. They
> are written infrequently so not overburdensome, but the clarity is a
> good reward. Locals by contrast quite often are more readable when using
> (consistent) shorthand, or at least I think so.
> -Chris

Sure, makes sense. I'll rename a few things and resend.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-13 21:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 19:13 [PATCH 1/5] drm/i915: Move a bunch of workaround-related code to its own file Oscar Mateo
2018-02-13 19:13 ` [PATCH 2/5] drm/i915: Split out functions for different kinds of workarounds Oscar Mateo
2018-02-13 20:54   ` Chris Wilson
2018-02-13 21:36     ` Oscar Mateo
2018-02-13 21:49       ` Chris Wilson
2018-02-13 19:13 ` [PATCH 3/5] drm/i915: Move WA BB stuff to the workarounds file as well Oscar Mateo
2018-02-13 19:13 ` [PATCH 4/5] drm/i915: Create a new category of display WAs Oscar Mateo
2018-02-13 20:02   ` Jani Nikula
2018-02-13 20:50     ` Chris Wilson
2018-02-13 21:34       ` Oscar Mateo [this message]
2018-02-13 19:13 ` [PATCH 5/5] drm/i915: Classify GT & Display WAs correctly Oscar Mateo
2018-02-13 19:37 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] drm/i915: Move a bunch of workaround-related code to its own file 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=3114cf07-1551-6c58-62c7-3921d91287ae@intel.com \
    --to=oscar.mateo@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=rodrigo.vivi@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.