From: Andi Shyti <andi.shyti@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/4] drm/i915/uapi: Add kerneldoc for engine class enum
Date: Thu, 28 Apr 2022 14:59:55 +0200 [thread overview]
Message-ID: <YmqPy6g/dCbg2XSt@intel.intel> (raw)
In-Reply-To: <20220428041926.1483683-2-matthew.d.roper@intel.com>
Hi Matt,
On Wed, Apr 27, 2022 at 09:19:23PM -0700, Matt Roper wrote:
> We'll be adding a new type of engine soon. Let's document the existing
> engine classes first to help make it clear what each type of engine is
> used for.
>
> Cc: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thank you for splitting this patch,
Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Andi Shyti <andi.shyti@linux.intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] drm/i915/uapi: Add kerneldoc for engine class enum
Date: Thu, 28 Apr 2022 14:59:55 +0200 [thread overview]
Message-ID: <YmqPy6g/dCbg2XSt@intel.intel> (raw)
In-Reply-To: <20220428041926.1483683-2-matthew.d.roper@intel.com>
Hi Matt,
On Wed, Apr 27, 2022 at 09:19:23PM -0700, Matt Roper wrote:
> We'll be adding a new type of engine soon. Let's document the existing
> engine classes first to help make it clear what each type of engine is
> used for.
>
> Cc: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thank you for splitting this patch,
Andi
next prev parent reply other threads:[~2022-04-28 13:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 4:19 [Intel-gfx] [PATCH v2 0/4] i915: Turn on compute engine support Matt Roper
2022-04-28 4:19 ` Matt Roper
2022-04-28 4:19 ` [Intel-gfx] [PATCH v2 1/4] drm/i915/uapi: Add kerneldoc for engine class enum Matt Roper
2022-04-28 4:19 ` Matt Roper
2022-04-28 12:59 ` Andi Shyti [this message]
2022-04-28 12:59 ` Andi Shyti
2022-04-28 4:19 ` [Intel-gfx] [PATCH v2 2/4] drm/i915/xehp: Add register for compute engine's MMIO-based TLB invalidation Matt Roper
2022-04-28 4:19 ` Matt Roper
2022-04-28 8:34 ` [Intel-gfx] " Tvrtko Ursulin
2022-04-28 8:34 ` Tvrtko Ursulin
2022-04-28 12:13 ` [Intel-gfx] " Kumar Valsan, Prathap
2022-04-28 12:13 ` Kumar Valsan, Prathap
2022-04-28 4:19 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/xehp: Add compute engine ABI Matt Roper
2022-04-28 4:19 ` Matt Roper
2022-04-28 7:58 ` [Intel-gfx] " Tvrtko Ursulin
2022-04-28 7:58 ` Tvrtko Ursulin
2022-04-28 13:04 ` [Intel-gfx] " Andi Shyti
2022-04-28 4:19 ` [Intel-gfx] [PATCH v2 4/4] drm/i915: Xe_HP SDV and DG2 have up to 4 CCS engines Matt Roper
2022-04-28 4:19 ` Matt Roper
2022-04-28 4:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for i915: Turn on compute engine support (rev4) Patchwork
2022-04-28 4:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-28 6:18 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-04-29 21:47 ` Matt Roper
2022-04-29 21:23 ` [Intel-gfx] [PATCH v2 0/4] i915: Turn on compute engine support Jordan Justen
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=YmqPy6g/dCbg2XSt@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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.