public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Chethan C <mail.chethanc@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hans Verkuil <hverkuil+cisco@kernel.org>,
	Kees Cook <kees@kernel.org>, Petr Mladek <pmladek@suse.com>,
	Osama Albahrani <osalbahr@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] staging: media: av7110: fix coding style
Date: Tue, 24 Mar 2026 14:08:57 +0200	[thread overview]
Message-ID: <acJ-2eBSlbuZ2ltN@ashevche-desk.local> (raw)
In-Reply-To: <20260323190835.660111-1-mail.chethanc@gmail.com>

On Tue, Mar 24, 2026 at 12:38:19AM +0530, Chethan C wrote:
> Fixed Indentation, Alignment issues reported by checkpatch.pl.
> 
> Rename enum av7110_rec_play_state, av7110_type_rec_play_format and
> av7110_encoder_command to follow the kernel naming style.
> 
> Rename wssData to wss_data to avoid CamelCase identifiers.

...

>  	u16			wssMode;
> -	u16			wssData;
> +	u16			wss_data;

Now these two are in inconsistent state.

...

> -	ret = av7110_fw_cmd(av7110, COMTYPE_ENCODER, LoadVidCode, 1, mode);
> +	ret = av7110_fw_cmd(av7110, COMTYPE_ENCODER, AV7110_LOAD_VID_CODE,
> +			    1, mode);

Also rethink about more logical split. As far as I can see this API does some
variadic arguments processing while the first two are mandatory ones. With
that taken into account I would do it as

	ret = av7110_fw_cmd(av7110, COMTYPE_ENCODER,
			    AV7110_LOAD_VID_CODE, 1, mode);

Also check the entire patch for this kind of amendments.

...

> -	rc = av7110_fw_cmd(av7110, COMTYPE_ENCODER, SetWSSConfig, 2, 1, av7110->wssData);

> +	rc = av7110_fw_cmd(av7110, COMTYPE_ENCODER, AV7110_SET_WSS_CONFIG, 2,
> +			   1, av7110->wss_data);
>  	return (rc < 0) ? rc : count;

This can also be improved a bit as

	if (rc)
		return rc;

	return count;

but strictly speaking it's out of the scope of this patch.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2026-03-24 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 19:08 [PATCH v5] staging: media: av7110: fix coding style Chethan C
2026-03-24 12:08 ` Andy Shevchenko [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=acJ-2eBSlbuZ2ltN@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil+cisco@kernel.org \
    --cc=kees@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mail.chethanc@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=osalbahr@gmail.com \
    --cc=pmladek@suse.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