public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: lijian_8010a29@163.com, mchehab@kernel.org,
	hverkuil-cisco@xs4all.nl, laurent.pinchart@ideasonboard.com,
	arnd@arndb.de, sakari.ailus@linux.intel.com,
	sergey.senozhatsky@gmail.com, gustavoars@kernel.org,
	yepeilin.cs@gmail.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	lijian <lijian@yulong.com>
Subject: Re: [PATCH v2] media: v4l2-ioctl: deleted the repeated word 'the' in the comments
Date: Wed, 26 May 2021 23:48:21 -0700	[thread overview]
Message-ID: <39c5f5ea0367aa3bcfecc8c0ff2d6bb84f927d0c.camel@perches.com> (raw)
In-Reply-To: <20210527064107.149950-1-lijian_8010a29@163.com>

On Thu, 2021-05-27 at 14:41 +0800, lijian_8010a29@163.com wrote:
> From: lijian <lijian@yulong.com>
> 
> deleted the repeated word 'the' in the comments of function
> v4l_sanitize_format()

Please update the suggested commit log message too as it
doesn't match the patch.

> ---
> v2: changed the repeated word 'the' to 'that' in the comments of
> function v4l_sanitize_format()
[]
> diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c b/drivers/media/v4l2-core/v4l2-ioctl.c
[]
> @@ -999,7 +999,7 @@ static void v4l_sanitize_format(struct v4l2_format *fmt)
>  	/*
>  	 * The v4l2_pix_format structure has been extended with fields that were
>  	 * not previously required to be set to zero by applications. The priv
> -	 * field, when set to a magic value, indicates the extended fields
> +	 * field, when set to a magic value, indicates that the extended fields
>  	 * are valid. Otherwise they will contain undefined values. To simplify
>  	 * the API towards drivers zero the extended fields and set the priv
>  	 * field to the magic value when the extended pixel format structure



      reply	other threads:[~2021-05-27  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  6:41 [PATCH v2] media: v4l2-ioctl: deleted the repeated word 'the' in the comments lijian_8010a29
2021-05-27  6:48 ` Joe Perches [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=39c5f5ea0367aa3bcfecc8c0ff2d6bb84f927d0c.camel@perches.com \
    --to=joe@perches.com \
    --cc=arnd@arndb.de \
    --cc=gustavoars@kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lijian@yulong.com \
    --cc=lijian_8010a29@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=yepeilin.cs@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