public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Wardle <matt@mattwardle.net>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Andy Shevchenko <andy@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: media: atomisp: Fix braces on incorrect lines
Date: Mon, 09 Feb 2026 18:05:25 +0000 (UTC)	[thread overview]
Message-ID: <aYoh4RKXOoezheVj@thinkpad> (raw)
In-Reply-To: <aYoATsI9KB8bgwjz@smile.fi.intel.com>

On Mon, Feb 09, 2026 at 05:42:06PM +0200, Andy Shevchenko wrote:
> On Mon, Feb 09, 2026 at 02:29:07PM +0000, Matt Wardle wrote:
> > Fix checkpatch.pl errors:
> > 
> > ERROR: open brace '{' following function definitions go on the next line
> > ERROR: that open brace { should be on the previous line
> 
> Nice! My comments below.
> 
> ...
> 
> > store_dvs_6axis_config(
> 
> >      const struct ia_css_dvs_6axis_config *dvs_6axis_config,
> >      const struct ia_css_binary *binary,
> >      const struct ia_css_frame_info *dvs_in_frame_info,
> > -    ia_css_ptr ddr_addr_y) {
> > +    ia_css_ptr ddr_addr_y)
> > +{
> 
> This makes no sense to touch before the parameters are indented correctly.
> I dunno if open parenthesis is fine at the end of the line, but I would do it
> differently, as
> 
> store_dvs_6axis_config(const struct ia_css_dvs_6axis_config *dvs_6axis_config,
> 		       const struct ia_css_binary *binary,
> 		       ...)
> {
> 
> ...
> 
> The bottom line is, you need to check manually these and make prerequisite
> patch to first fix the indentation.
> 
> ...
> 
> >  int
> >  ia_css_get_dvs2_statistics(
> >      struct ia_css_dvs2_statistics          *host_stats,
> > -    const struct ia_css_isp_dvs_statistics *isp_stats) {
> > +    const struct ia_css_isp_dvs_statistics *isp_stats)
> > +{
> 
> Ditto.
> 
> And when you go with indentation it makes sense to combine (it's fine in this
> case) those changes with the splitting { to the next line.

Thanks, I'll fix the indentation first on the functions then resubmit
without the last patch.

This is happening in many files so it might be best I tackle the other
occurences in a separate patch.

  reply	other threads:[~2026-02-09 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 14:29 [PATCH 0/3] staging: media: atomisp: Fix brace style issues Matt Wardle
2026-02-09 14:29 ` [PATCH 1/3] staging: media: atomisp: Fix braces on incorrect lines Matt Wardle
2026-02-09 15:42   ` Andy Shevchenko
2026-02-09 18:05     ` Matt Wardle [this message]
2026-02-09 14:29 ` [PATCH 2/3] staging: media: atomisp: Remove braces for single statement blocks Matt Wardle
2026-02-09 15:37   ` Andy Shevchenko
2026-02-09 14:29 ` [PATCH 3/3] staging: media: atomisp: Fix missing braces for " Matt Wardle
2026-02-09 15:44   ` Andy Shevchenko

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=aYoh4RKXOoezheVj@thinkpad \
    --to=matt@mattwardle.net \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.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