Hi Randy, On 17 August 2016 at 05:01, Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: > From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> > > Fix dma-buf kernel-doc warning and 2 minor typos in > fence_array_create(). > Thanks for your patch, I will queue it up! > Fixes this warning: > ..//drivers/dma-buf/fence-array.c:124: warning: No description found for parameter 'signal_on_any' > > Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> > Cc: Sumit Semwal <sumit.semwal@xxxxxxxxxx> > Cc: linux-media@xxxxxxxxxxxxxxx > Cc: dri-devel@xxxxxxxxxxxxxxxxxxxxx > Cc: linaro-mm-sig@xxxxxxxxxxxxxxxx > --- > drivers/dma-buf/fence-array.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > --- lnx-48-rc2.orig/drivers/dma-buf/fence-array.c > +++ lnx-48-rc2/drivers/dma-buf/fence-array.c > @@ -106,14 +106,14 @@ const struct fence_ops fence_array_ops = > * @fences: [in] array containing the fences > * @context: [in] fence context to use > * @seqno: [in] sequence number to use > - * @signal_on_any [in] signal on any fence in the array > + * @signal_on_any: [in] signal on any fence in the array > * > * Allocate a fence_array object and initialize the base fence with fence_init(). > * In case of error it returns NULL. > * > - * The caller should allocte the fences array with num_fences size > + * The caller should allocate the fences array with num_fences size > * and fill it with the fences it wants to add to the object. Ownership of this > - * array is take and fence_put() is used on each fence on release. > + * array is taken and fence_put() is used on each fence on release. > * > * If @signal_on_any is true the fence array signals if any fence in the array > * signals, otherwise it signals when all fences in the array signal. Best, Sumit. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
