Messages in this thread | | | Date | Mon, 2 Apr 2012 09:49:19 -0500 | Subject | Re: [PATCH]NEXT:drivers:staging:omapdrm Fix typos in drivers:omapdrm | From | "Clark, Rob" <> |
| |
On Mon, Apr 2, 2012 at 9:25 AM, Justin P. Mattock <justinmattock@gmail.com> wrote: > From: "Justin P. Mattock" <justinmattock@gmail.com> > > The below patch fixes some typos that I found while reading. > Note: I was told to hold off sending anything until *rc1 so hopefully > now its alright.(wasnt sure what kernel *rc*) > > Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
Thanks
Reviewed-by: Rob Clark <rob@ti.com>
> > --- > drivers/staging/omapdrm/omap_fb.c | 2 +- > drivers/staging/omapdrm/tcm-sita.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/staging/omapdrm/omap_fb.c b/drivers/staging/omapdrm/omap_fb.c > index 04b235b..0c53a3c 100644 > --- a/drivers/staging/omapdrm/omap_fb.c > +++ b/drivers/staging/omapdrm/omap_fb.c > @@ -167,7 +167,7 @@ void omap_framebuffer_update_scanout(struct drm_framebuffer *fb, int x, int y, > } > > /* Call for unpin 'a' (if not NULL), and pin 'b' (if not NULL). Although > - * buffers to unpin are just just pushed to the unpin fifo so that the > + * buffers to unpin are just pushed to the unpin fifo so that the > * caller can defer unpin until vblank. > * > * Note if this fails (ie. something went very wrong!), all buffers are > diff --git a/drivers/staging/omapdrm/tcm-sita.c b/drivers/staging/omapdrm/tcm-sita.c > index 10d5ac3..efb6095 100644 > --- a/drivers/staging/omapdrm/tcm-sita.c > +++ b/drivers/staging/omapdrm/tcm-sita.c > @@ -200,7 +200,7 @@ static s32 sita_reserve_1d(struct tcm *tcm, u32 num_slots, > * > * @param w width > * @param h height > - * @param area pointer to the area that will be populated with the reesrved > + * @param area pointer to the area that will be populated with the reserved > * area > * > * @return 0 on success, non-0 error value on failure. > -- > 1.7.5.4 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |