From: Johts <johatanrlima@gmail.com>
To: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, andy@kernel.org, hansg@kernel.org,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
regkh@linuxfoundation.org
Cc: ~lkcamp/patches@lists.sr.ht, koike@igalia.com,
Johts <johatanrlima@gmail.com>
Subject: [PATCH] staging: media: atomisp: pci: runtime: debug: src: remove curly braces for single line if
Date: Thu, 23 Apr 2026 15:45:40 -0300 [thread overview]
Message-ID: <20260423184543.109954-1-johatanrlima@gmail.com> (raw)
Fix checkpath error "WARNING: braces {} are not necessary for single statement blocks" in sh_css_params.c:1931
Signed-off-by: Johts <johatanrlima@gmail.com>
---
drivers/staging/media/atomisp/pci/sh_css_params.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/sh_css_params.c b/drivers/staging/media/atomisp/pci/sh_css_params.c
index fcebace11daf..31426001864e 100644
--- a/drivers/staging/media/atomisp/pci/sh_css_params.c
+++ b/drivers/staging/media/atomisp/pci/sh_css_params.c
@@ -1928,10 +1928,8 @@ sh_css_set_per_frame_isp_config_on_pipe(
params = stream->per_frame_isp_params_configs;
/* update new ISP params object with the new config */
- if (!sh_css_init_isp_params_from_global(stream, params, false, pipe)) {
- err1 = -EINVAL;
- }
-
+ if (!sh_css_init_isp_params_from_global(stream, params, false, pipe)) err1 = -EINVAL;
+
err2 = sh_css_init_isp_params_from_config(stream->pipes[0], params, config, pipe);
if (per_frame_config_created) {
--
2.43.0
next reply other threads:[~2026-04-23 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:45 Johts [this message]
2026-04-23 21:04 ` [PATCH] staging: media: atomisp: pci: runtime: debug: src: remove curly braces for single line if Sakari Ailus
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=20260423184543.109954-1-johatanrlima@gmail.com \
--to=johatanrlima@gmail.com \
--cc=andy@kernel.org \
--cc=hansg@kernel.org \
--cc=koike@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=regkh@linuxfoundation.org \
--cc=sakari.ailus@linux.intel.com \
--cc=~lkcamp/patches@lists.sr.ht \
/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