public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Lad Prabhakar <prabhakar.csengg@gmail.com>
Cc: LMML <linux-media@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH] videodev2.h: fix typos
Date: Mon, 20 May 2013 12:58:47 +0200	[thread overview]
Message-ID: <5288300.PnnGMIV8gA@avalon> (raw)
In-Reply-To: <1369044160-7571-1-git-send-email-prabhakar.csengg@gmail.com>

Hi Prabhakar,

Thank you for the patch.

On Monday 20 May 2013 15:32:40 Lad Prabhakar wrote:
> From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> 
> This patch fixes several typos in videodev2.h file
> 
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  include/uapi/linux/videodev2.h |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> index f40b41c..ee4af53 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
> @@ -555,7 +555,7 @@ struct v4l2_jpegcompression {
>  	__u32 jpeg_markers;     /* Which markers should go into the JPEG
>  				 * output. Unless you exactly know what
>  				 * you do, leave them untouched.
> -				 * Inluding less markers will make the
> +				 * Including less markers will make the
>  				 * resulting code smaller, but there will
>  				 * be fewer applications which can read it.
>  				 * The presence of the APP and COM marker
> @@ -567,7 +567,7 @@ struct v4l2_jpegcompression {
>  #define V4L2_JPEG_MARKER_DRI (1<<5)    /* Define Restart Interval */
>  #define V4L2_JPEG_MARKER_COM (1<<6)    /* Comment segment */
>  #define V4L2_JPEG_MARKER_APP (1<<7)    /* App segment, driver will
> -					* allways use APP0 */
> +					* always use APP0 */
>  };
> 
>  /*
> @@ -900,7 +900,7 @@ typedef __u64 v4l2_std_id;
>  /*
>   * "Common" PAL - This macro is there to be compatible with the old
>   * V4L1 concept of "PAL": /BGDKHI.
> - * Several PAL standards are mising here: /M, /N and /Nc
> + * Several PAL standards are missing here: /M, /N and /Nc
>   */
>  #define V4L2_STD_PAL		(V4L2_STD_PAL_BG	|\
>  				 V4L2_STD_PAL_DK	|\
> @@ -1790,7 +1790,7 @@ struct v4l2_event_subscription {
>  #define V4L2_CHIP_MATCH_HOST V4L2_CHIP_MATCH_BRIDGE
>  #define V4L2_CHIP_MATCH_I2C_DRIVER  1  /* Match against I2C driver name */
>  #define V4L2_CHIP_MATCH_I2C_ADDR    2  /* Match against I2C 7-bit address
> */ -#define V4L2_CHIP_MATCH_AC97        3  /* Match against anciliary AC97
> chip */ +#define V4L2_CHIP_MATCH_AC97        3  /* Match against ancillary
> AC97 chip */ #define V4L2_CHIP_MATCH_SUBDEV      4  /* Match against subdev
> index */
> 
>  struct v4l2_dbg_match {
-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2013-05-20 10:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 10:02 [PATCH] videodev2.h: fix typos Lad Prabhakar
2013-05-20 10:58 ` 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=5288300.PnnGMIV8gA@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=prabhakar.csengg@gmail.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