Message ID | 33fda13b500b39645e7363806c6e458e915b581e.1657113304.git.geert@linux-m68k.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [v2] drm/fb: Improve drm_framebuffer.offsets documentation | expand |
Hi Geert, On Wed, Jul 06, 2022 at 03:16:18PM +0200, Geert Uytterhoeven wrote: > Fix various spelling and grammar mistakes in the kerneldoc comments > documenting the offsets member in the drm_framebuffer structure: > - s/laytou/layout/, > - Add missing "is", > - s/it/its/. > > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> > Acked-by: Sam Ravnborg <sam@ravnborg.org> > Reviewed-by: Simon Ser <contact@emersion.fr> More doc improvements - good! Applied to drm-misc (drm-misc-next). Sam
diff --git a/include/drm/drm_framebuffer.h b/include/drm/drm_framebuffer.h index f67c5b7bcb68654a..0dcc07b68654844b 100644 --- a/include/drm/drm_framebuffer.h +++ b/include/drm/drm_framebuffer.h @@ -154,10 +154,10 @@ struct drm_framebuffer { * drm_mode_fb_cmd2. * * Note that this is a linear offset and does not take into account - * tiling or buffer laytou per @modifier. It meant to be used when the - * actual pixel data for this framebuffer plane starts at an offset, - * e.g. when multiple planes are allocated within the same backing - * storage buffer object. For tiled layouts this generally means it + * tiling or buffer layout per @modifier. It is meant to be used when + * the actual pixel data for this framebuffer plane starts at an offset, + * e.g. when multiple planes are allocated within the same backing + * storage buffer object. For tiled layouts this generally means its * @offsets must at least be tile-size aligned, but hardware often has * stricter requirements. *