From 6d52ef878365b0cb6610c9c20601c2b2d31639ed Mon Sep 17 00:00:00 2001 From: Janusz Krzysztofik Date: Tue, 2 Nov 2010 12:30:48 -0300 Subject: [PATCH] --- yaml --- r: 222068 b: refs/heads/master c: 4b35e625da69654a71515444c1c0a6b6ce84ad2f h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/drivers/media/video/omap1_camera.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index b61daf93d424..bda662909458 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 8c66caebdace925f19fcfd2d1f026044c3995c4b +refs/heads/master: 4b35e625da69654a71515444c1c0a6b6ce84ad2f diff --git a/trunk/drivers/media/video/omap1_camera.c b/trunk/drivers/media/video/omap1_camera.c index 674f74e67443..cbfd07f2d9da 100644 --- a/trunk/drivers/media/video/omap1_camera.c +++ b/trunk/drivers/media/video/omap1_camera.c @@ -504,7 +504,7 @@ static void omap1_videobuf_queue(struct videobuf_queue *vq, * empty. Since the transfer of the DMA programming register set * content to the DMA working register set is done automatically * by the DMA hardware, this can pretty well happen while we - * are keeping the lock here. Levae fetching it from the queue + * are keeping the lock here. Leave fetching it from the queue * to be done when a next DMA interrupt occures instead. */ return;