All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Yu Dai <yu.dai@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/6] drm/i915/guc: Add GuC css header parser
Date: Mon, 28 Sep 2015 10:13:16 +0200	[thread overview]
Message-ID: <20150928081316.GP3383@phenom.ffwll.local> (raw)
In-Reply-To: <560576F8.3080505@intel.com>

On Fri, Sep 25, 2015 at 09:31:52AM -0700, Yu Dai wrote:
> Be note that I will use term *length* or *len* in header definition, which
> is in dwords unit. This is to avoid the confusion with *size*.

lenght is also generally in bytes. If you want to use separate variables
to avoid confusion I'd suggest num_dwords (treat it like an array of
dwords) or size_dw (_dw as the unit suffix, like we do with e.g. _usec).
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
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-09-28  8:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 23:56 [PATCH 0/6] Several GuC related patches yu.dai
2015-09-10 23:56 ` [PATCH 1/6] drm/i915/guc: Fix a bug in GuC status check yu.dai
2015-09-10 23:56 ` [PATCH 2/6] drm/i915/guc: Add GuC css header parser yu.dai
2015-09-14  9:28   ` Daniel Vetter
2015-09-10 23:56 ` [PATCH 3/6] drm/i915/guc: Add host2guc notification for suspend and resume yu.dai
2015-09-15 23:30   ` [PATCH 03/15] " yu.dai
2015-09-10 23:56 ` [PATCH 4/6] drm/i915/guc: Don't send flips to GuC yu.dai
2015-09-11 12:44   ` [PATCH v2 1/1] drm/i915: Direct all DE interrupts to host Sagar Arun Kamble
2015-09-21 19:02     ` O'Rourke, Tom
2015-09-10 23:56 ` [PATCH 5/6] drm/i915/guc: Media domain bit needed when notify GuC rc6 state yu.dai
2015-09-14  9:32   ` Daniel Vetter
2015-09-15 23:31   ` [PATCH 05/15] " yu.dai
2015-09-10 23:56 ` [PATCH 6/6] drm/i915/guc: Enable GuC submission, where supported yu.dai
2015-09-22 20:48 ` [PATCH v2 0/6] Several GuC related patches yu.dai
2015-09-22 20:48   ` [PATCH v2 1/6] drm/i915/guc: Fix a bug in GuC status check yu.dai
2015-09-24  4:59     ` Kamble, Sagar A
2015-09-28  8:10       ` Daniel Vetter
2015-09-22 20:48   ` [PATCH v2 2/6] drm/i915/guc: Add GuC css header parser yu.dai
2015-09-24 14:23     ` Dave Gordon
2015-09-24 18:34       ` Yu Dai
2015-09-24 19:04         ` Dave Gordon
2015-09-24 20:23           ` Yu Dai
2015-09-25 14:45             ` Jani Nikula
2015-09-25 16:31               ` Yu Dai
2015-09-28  8:13                 ` Daniel Vetter [this message]
2015-09-22 20:48   ` [PATCH v2 3/6] drm/i915/guc: Add host2guc notification for suspend and resume yu.dai
2015-09-24  8:27     ` Kamble, Sagar A
2015-09-22 20:48   ` [PATCH v2 4/6] drm/i915/guc: Don't send flips to GuC yu.dai
2015-09-22 23:11     ` [PATCH] " yu.dai
2015-09-23  0:56       ` O'Rourke, Tom
2015-09-22 20:48   ` [PATCH v2 5/6] drm/i915/guc: Media domain bit needed when notify GuC rc6 state yu.dai
2015-09-23  0:59     ` O'Rourke, Tom
2015-09-23  8:37       ` Daniel Vetter
2015-09-22 20:48   ` [PATCH v2 6/6] drm/i915/guc: Enable GuC submission, where supported yu.dai
2015-09-22 23:13     ` [PATCH] " yu.dai

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=20150928081316.GP3383@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=yu.dai@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.