From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Manuel Rodriguez <manuel2982@gmail.com>
Cc: mchehab@osg.samsung.com, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: media: davinci_vpfe: Fix spelling error on a comment
Date: Tue, 22 Nov 2016 23:35:23 +0200 [thread overview]
Message-ID: <1625650.Ctaqjj1OdI@avalon> (raw)
In-Reply-To: <1457421366-4146-1-git-send-email-manuel2982@gmail.com>
Hi Manuel,
Thank you for the patch and sorry for the late reply.
On Tuesday 08 Mar 2016 01:16:06 Manuel Rodriguez wrote:
> Fix spelling error on a comment, change 'wether' to 'whether'
>
> Signed-off-by: Manuel Rodriguez <manuel2982@gmail.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
and applied to my tree. I will send a pull request for v4.11.
> ---
> drivers/staging/media/davinci_vpfe/vpfe_video.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/davinci_vpfe/vpfe_video.c
> b/drivers/staging/media/davinci_vpfe/vpfe_video.c index 0a65405..e4b953a
> 100644
> --- a/drivers/staging/media/davinci_vpfe/vpfe_video.c
> +++ b/drivers/staging/media/davinci_vpfe/vpfe_video.c
> @@ -195,7 +195,7 @@ static int vpfe_update_pipe_state(struct
> vpfe_video_device *video) return 0;
> }
>
> -/* checks wether pipeline is ready for enabling */
> +/* checks whether pipeline is ready for enabling */
> int vpfe_video_is_pipe_ready(struct vpfe_pipeline *pipe)
> {
> int i;
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-11-22 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 7:16 [PATCH] Staging: media: davinci_vpfe: Fix spelling error on a comment Manuel Rodriguez
2016-11-22 21:35 ` Laurent Pinchart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1625650.Ctaqjj1OdI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manuel2982@gmail.com \
--cc=mchehab@osg.samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox