gbm: doc fixes

Signed-off-by: Eric Engestrom <eric.engestrom@imgtec.com>
Reviewed-by: Chad Versace <chad.versace@intel.com>
This commit is contained in:
Eric Engestrom 2016-06-23 12:00:44 +01:00 committed by Chad Versace
parent 60a27ad122
commit b293e8b470
2 changed files with 4 additions and 4 deletions

View file

@ -232,7 +232,7 @@ gbm_bo_get_handle(struct gbm_bo *bo)
/** Get a DMA-BUF file descriptor for the buffer object
*
* This function creates a DMA-BUF (also known as PRIME) file descriptor
* handle for the buffer object. Eeach call to gbm_bo_get_fd() returns a new
* handle for the buffer object. Each call to gbm_bo_get_fd() returns a new
* file descriptor and the caller is responsible for closing the file
* descriptor.
@ -249,8 +249,8 @@ gbm_bo_get_fd(struct gbm_bo *bo)
/** Write data into the buffer object
*
* If the buffer object was created with the GBM_BO_USE_WRITE flag,
* this function can used to write data into the buffer object. The
* data is copied directly into the object and it's the responsiblity
* this function can be used to write data into the buffer object. The
* data is copied directly into the object and it's the responsibility
* of the caller to make sure the data represents valid pixel data,
* according to the width, height, stride and format of the buffer object.
*

View file

@ -207,7 +207,7 @@ enum gbm_bo_flags {
GBM_BO_USE_RENDERING = (1 << 2),
/**
* Buffer can be used for gbm_bo_write. This is guaranteed to work
* with GBM_BO_USE_CURSOR. but may not work for other combinations.
* with GBM_BO_USE_CURSOR, but may not work for other combinations.
*/
GBM_BO_USE_WRITE = (1 << 3),
/**