public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Nick Hoath <nicholas.hoath@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 03/10] drm/i915: gen 9 h/w w/a (WaDisablePartialInstShootdown)
Date: Mon, 9 Feb 2015 19:10:17 +0100	[thread overview]
Message-ID: <20150209181017.GE24485@phenom.ffwll.local> (raw)
In-Reply-To: <54D48B08.3080603@intel.com>

On Fri, Feb 06, 2015 at 09:36:08AM +0000, Nick Hoath wrote:
> On 06/02/2015 08:52, Daniel Vetter wrote:
> >On Thu, Feb 05, 2015 at 05:51:46PM +0000, Damien Lespiau wrote:
> >>On Thu, Feb 05, 2015 at 10:47:18AM +0000, Nick Hoath wrote:
> >>>From: "Hoath, Nicholas" <nicholas.hoath@intel.com>
> >>>
> >>>Add:
> >>>WaDisablePartialInstShootdown
> >>
> >>Just an editor note: that's not really additional information compared
> >>to the subject of the patch. Also subject message could be a bit more
> >>direct and mention SKL:
> >>
> >>   drm/i915/skl: Implement WaDisablePartialInstShootdown
> >
> >Well it's gen9 but yeah. The commit message body should explain the
> >commit (e.g. more details on impact), but for w/a that's only really
> >required if there's been an outside report.
> So an empty body is ok if the subject has sufficient information?

Yeah for hw wa there's often not more to say. Except when some details
about the impact are known which are relevant (e.g. existing bug report or
not wa for a feature not yet used in upstream).

Generally an empty commit message is a bit thin, but just repeating the
summar doesn't add value.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-02-09 18:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 10:47 [PATCH 00/10] drm/i915: HardWare WorkArounds for gen 9 Nick Hoath
2015-02-05 10:47 ` [PATCH 01/10] drm/i915: ring w/a initialisation " Nick Hoath
2015-02-05 17:39   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 02/10] drm/i915: ring w/a gen 9 revision definitions Nick Hoath
2015-02-05 17:46   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 03/10] drm/i915: gen 9 h/w w/a (WaDisablePartialInstShootdown) Nick Hoath
2015-02-05 17:51   ` Damien Lespiau
2015-02-06  8:52     ` Daniel Vetter
2015-02-06  9:36       ` Nick Hoath
2015-02-09 18:10         ` Daniel Vetter [this message]
2015-02-05 10:47 ` [PATCH 04/10] drm/i915: gen 9 h/w w/a (WaDisableDgMirrorFixInHalfSliceChicken5) Nick Hoath
2015-02-05 17:55   ` Damien Lespiau
2015-02-05 17:57     ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 05/10] drm/i915: gen 9 h/w w/a (syncing dependencies between camera and graphics) Nick Hoath
2015-02-05 18:00   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 06/10] drm/i915: gen 9 h/w w/a (WaDisableSDEUnitClockGating) Nick Hoath
2015-02-05 18:01   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 07/10] drm/i915: gen 9 h/w w/a (WaEnableYV12BugFixInHalfSliceChicken7) Nick Hoath
2015-02-05 18:04   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 08/10] drm/i915: gen 9 h/w w/a (Wa4x4STCOptimizationDisable) Nick Hoath
2015-02-05 18:05   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 09/10] drm/i915: gen 9 h/w w/a (WaForceEnableNonCoherent) Nick Hoath
2015-02-05 18:10   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 10/10] drm/i915: gen 9 h/w w/a (WaEnableForceRestoreInCtxtDescForVCS) Nick Hoath
2015-02-05 17:27   ` shuang.he
2015-02-05 18:17   ` Damien Lespiau

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=20150209181017.GE24485@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nicholas.hoath@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox