linux-kernel - Re: [PATCH 1/2] staging: media: atomisp: fix block comment style in ov2722.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2026020950-pacific-concur-9b99@gregkh>
Date: Mon, 9 Feb 2026 07:47:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Taekyung Oh <ohxorud@...orud.com>
Cc: Hans de Goede <hansg@...nel.org>,
	Mauro Carvalho Chehab <mchehab@...nel.org>,
	Andy Shevchenko <andy@...nel.org>,
	Sakari Ailus <sakari.ailus@...ux.intel.com>,
	linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] staging: media: atomisp: fix block comment style in
 ov2722.h

On Mon, Feb 09, 2026 at 04:55:53AM +0000, Taekyung Oh wrote:
> Fix coding style warnings reported by checkpatch.pl.
> Move the comments above the corresponding code lines.
> 
> Signed-off-by: Taekyung Oh <ohxorud@...orud.com>
> ---
>  drivers/staging/media/atomisp/i2c/ov2722.h | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/staging/media/atomisp/i2c/ov2722.h b/drivers/staging/media/atomisp/i2c/ov2722.h
> index 00317d105..c69f0086c 100644
> --- a/drivers/staging/media/atomisp/i2c/ov2722.h
> +++ b/drivers/staging/media/atomisp/i2c/ov2722.h
> @@ -566,8 +566,8 @@ static const struct ov2722_reg ov2722_VGA_30fps[] = {
>  #endif
>  
>  static const struct ov2722_reg ov2722_1632_1092_30fps[] = {
> -	{OV2722_8BIT, 0x3021, 0x03}, /* For stand wait for
> -				a whole frame complete.(vblank) */
> +    /* For stand wait for a whole frame complete.(vblank) */
> +	{OV2722_8BIT, 0x3021, 0x03},

You now added a different coding style warning :(