public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Matt Wardle <matt@mattwardle.net>
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 3/3] staging: media: atomisp: Fix missing braces for statement blocks
Date: Mon, 9 Feb 2026 17:44:02 +0200	[thread overview]
Message-ID: <aYoAwhiT5kD7aJ86@smile.fi.intel.com> (raw)
In-Reply-To: <20260209142820.650334-4-matt@mattwardle.net>

On Mon, Feb 09, 2026 at 02:29:28PM +0000, Matt Wardle wrote:
> Fix checkpatch.pl checks:
> 
> CHECK: Unbalanced braces around else statement
> CHECK: braces {} should be used on all arms of this statement
> CHECK: Blank lines aren't necessary before a close brace '}'

OK, but I think this one can wait. This most likely doesn't affect readability
in any better way (so, w/o this patch it's not worse than after).

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2026-02-09 15:44 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
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 [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=aYoAwhiT5kD7aJ86@smile.fi.intel.com \
    --to=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=matt@mattwardle.net \
    --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