summaryrefslogtreecommitdiff
path: root/src/gallium/include/pipe
diff options
context:
space:
mode:
authorBrian Paul <brianp@vmware.com>2010-04-22 11:33:26 -0600
committerBrian Paul <brianp@vmware.com>2010-04-22 11:33:26 -0600
commit50d77c79fbcdf6a33691bfa120d54528d28091a4 (patch)
tree5cff375326c6993d2df0984a472830f2f2b211a3 /src/gallium/include/pipe
parent1143221cfd4c42e7767f8ccaefb00e145b7d5efe (diff)
gallium: fix comment language, remove dangling comment
Diffstat (limited to 'src/gallium/include/pipe')
-rw-r--r--src/gallium/include/pipe/p_defines.h8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/gallium/include/pipe/p_defines.h b/src/gallium/include/pipe/p_defines.h
index 0a4bd584ae..48edfbfcce 100644
--- a/src/gallium/include/pipe/p_defines.h
+++ b/src/gallium/include/pipe/p_defines.h
@@ -291,10 +291,10 @@ enum pipe_transfer_usage {
#define PIPE_BIND_TRANSFER_READ (1 << 10) /* get_transfer */
#define PIPE_BIND_CUSTOM (1 << 16) /* state-tracker/winsys usages */
-/* The first two flags were previously part of the amorphous
+/* The first two flags above were previously part of the amorphous
* TEXTURE_USAGE, most of which are now descriptions of the ways a
- * particular texture can be bound to the gallium pipeline. These two
- * do not fit within that and probably need to be migrated to some
+ * particular texture can be bound to the gallium pipeline. The two flags
+ * below do not fit within that and probably need to be migrated to some
* other place.
*
* It seems like scanout is used by the Xorg state tracker to ask for
@@ -304,7 +304,7 @@ enum pipe_transfer_usage {
*
* The shared flag is quite underspecified, but certainly isn't a
* binding flag - it seems more like a message to the winsys to create
- * a shareable allocation. Could it mean that this texture is a valid argument for
+ * a shareable allocation.
*/
#define PIPE_BIND_SCANOUT (1 << 14) /* */
#define PIPE_BIND_SHARED (1 << 15) /* get_texture_handle ??? */