Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v1 3/5] drm-uapi/i915: sync with drm-next
Date: Tue,  7 Nov 2023 18:43:47 +0100	[thread overview]
Message-ID: <20231107174349.60255-4-kamil.konieczny@linux.intel.com> (raw)
In-Reply-To: <20231107174349.60255-1-kamil.konieczny@linux.intel.com>

Sync with drm-next commit ("f2cab4b318ee8023f4ad640b906ae268942a7db4")

This is documentation cleanup.

Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: Janga Rahul Kumar<janga.rahul.kumar@intel.com>
Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
 include/drm-uapi/i915_drm.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/include/drm-uapi/i915_drm.h b/include/drm-uapi/i915_drm.h
index 0a5c81445..ce9fa2812 100644
--- a/include/drm-uapi/i915_drm.h
+++ b/include/drm-uapi/i915_drm.h
@@ -38,13 +38,13 @@ extern "C" {
  */
 
 /**
- * DOC: uevents generated by i915 on it's device node
+ * DOC: uevents generated by i915 on its device node
  *
  * I915_L3_PARITY_UEVENT - Generated when the driver receives a parity mismatch
- *	event from the gpu l3 cache. Additional information supplied is ROW,
+ *	event from the GPU L3 cache. Additional information supplied is ROW,
  *	BANK, SUBBANK, SLICE of the affected cacheline. Userspace should keep
- *	track of these events and if a specific cache-line seems to have a
- *	persistent error remap it with the l3 remapping tool supplied in
+ *	track of these events, and if a specific cache-line seems to have a
+ *	persistent error, remap it with the L3 remapping tool supplied in
  *	intel-gpu-tools.  The value supplied with the event is always 1.
  *
  * I915_ERROR_UEVENT - Generated upon error detection, currently only via
-- 
2.42.0

  parent reply	other threads:[~2023-11-07 17:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 17:43 [igt-dev] [PATCH i-g-t v1 0/5] drm-uapi: sync with drm-next f2cab4b318ee Kamil Konieczny
2023-11-07 17:43 ` [igt-dev] [PATCH i-g-t v1 1/5] include/drm-uapi: sync core headers with drm-next Kamil Konieczny
2023-11-07 17:54   ` Simon Ser
2023-11-08 14:00     ` Kamil Konieczny
2023-11-07 17:43 ` [igt-dev] [PATCH i-g-t v1 2/5] drm-uapi/amdgpu: sync " Kamil Konieczny
2023-11-07 18:35   ` vitaly prosyak
2023-11-07 17:43 ` Kamil Konieczny [this message]
2023-11-09  6:34   ` [igt-dev] [PATCH i-g-t v1 3/5] drm-uapi/i915: " Kumar, Janga Rahul
2023-11-07 17:43 ` [igt-dev] [PATCH i-g-t v1 4/5] drm-uapi/nouveau: " Kamil Konieczny
2023-11-08 20:41   ` Lyude Paul
2023-11-07 17:43 ` [igt-dev] [PATCH i-g-t v1 5/5] drm-uapi/virtgpu: " Kamil Konieczny
2023-11-09  6:36   ` Kumar, Janga Rahul
2023-11-07 18:50 ` [igt-dev] ✓ Fi.CI.BAT: success for drm-uapi: sync with drm-next f2cab4b318ee Patchwork
2023-11-07 19:23 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-08 11:12 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20231107174349.60255-4-kamil.konieczny@linux.intel.com \
    --to=kamil.konieczny@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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