On Wed, Jan 10, 2024 at 08:11:55PM -0800, Randy Dunlap wrote: > Fix spelling mistakes as reported by codespell. > > Signed-off-by: Randy Dunlap <[email protected]> > Cc: Sumit Semwal <[email protected]> > Cc: [email protected] > Cc: [email protected] > Cc: Christian König <[email protected]> > Cc: [email protected]
Both dma-buf spell fixes applied to drm-misc-next, thanks! -Sima > --- > drivers/dma-buf/dma-resv.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff -- a/drivers/dma-buf/dma-resv.c b/drivers/dma-buf/dma-resv.c > --- a/drivers/dma-buf/dma-resv.c > +++ b/drivers/dma-buf/dma-resv.c > @@ -405,7 +405,7 @@ static void dma_resv_iter_walk_unlocked( > * > * Beware that the iterator can be restarted. Code which accumulates > statistics > * or similar needs to check for this with dma_resv_iter_is_restarted(). For > - * this reason prefer the locked dma_resv_iter_first() whenver possible. > + * this reason prefer the locked dma_resv_iter_first() whenever possible. > * > * Returns the first fence from an unlocked dma_resv obj. > */ > @@ -428,7 +428,7 @@ EXPORT_SYMBOL(dma_resv_iter_first_unlock > * > * Beware that the iterator can be restarted. Code which accumulates > statistics > * or similar needs to check for this with dma_resv_iter_is_restarted(). For > - * this reason prefer the locked dma_resv_iter_next() whenver possible. > + * this reason prefer the locked dma_resv_iter_next() whenever possible. > * > * Returns the next fence from an unlocked dma_resv obj. > */ > _______________________________________________ > Linaro-mm-sig mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
