From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, boris.brezillon@bootlin.com,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Eric Anholt <eric@anholt.net>
Subject: [PATCH 1/4] drm/v3d: Fix whitespace inconsistency in the header.
Date: Thu, 8 Nov 2018 08:16:51 -0800 [thread overview]
Message-ID: <20181108161654.19888-2-eric@anholt.net> (raw)
In-Reply-To: <20181108161654.19888-1-eric@anholt.net>
Signed-off-by: Eric Anholt <eric@anholt.net>
---
include/uapi/drm/v3d_drm.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/drm/v3d_drm.h b/include/uapi/drm/v3d_drm.h
index f446656d00b1..b1e5de076b0f 100644
--- a/include/uapi/drm/v3d_drm.h
+++ b/include/uapi/drm/v3d_drm.h
@@ -66,7 +66,7 @@ struct drm_v3d_submit_cl {
*/
__u32 bcl_start;
- /** End address of the BCL (first byte after the BCL) */
+ /** End address of the BCL (first byte after the BCL) */
__u32 bcl_end;
/* Offset of the render command list.
@@ -82,7 +82,7 @@ struct drm_v3d_submit_cl {
*/
__u32 rcl_start;
- /** End address of the RCL (first byte after the RCL) */
+ /** End address of the RCL (first byte after the RCL) */
__u32 rcl_end;
/** An optional sync object to wait on before starting the BCL. */
--
2.19.1
next prev parent reply other threads:[~2018-11-08 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 16:16 [PATCH 0/4] V3D TFU engine support Eric Anholt
2018-11-08 16:16 ` Eric Anholt [this message]
2018-11-13 10:22 ` [PATCH 1/4] drm/v3d: Fix whitespace inconsistency in the header Boris Brezillon
2018-11-08 16:16 ` [PATCH 2/4] drm/v3d: Update a comment about what uses v3d_job_dependency() Eric Anholt
2018-11-13 10:22 ` Boris Brezillon
2018-11-08 16:16 ` [PATCH 3/4] drm/v3d: Clean up the reservation object setup Eric Anholt
2018-11-13 10:22 ` Boris Brezillon
2018-11-08 16:16 ` [PATCH 4/4] drm/v3d: Add support for submitting jobs to the TFU Eric Anholt
2018-11-13 22:03 ` Eric Anholt
2018-11-28 19:45 ` Dave Emett
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=20181108161654.19888-2-eric@anholt.net \
--to=eric@anholt.net \
--cc=boris.brezillon@bootlin.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).