From: Mani Bharadwaj <manibharadwajcr@gmail.com>
To: hansg@kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, andy@kernel.org,
gregkh@linuxfoundation.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Mani Bharadwaj <manibharadwajcr@gmail.com>
Subject: [PATCH v3] staging: media: atomisp: anr: move trailing statement to its own line
Date: Tue, 23 Jun 2026 00:11:00 +0530 [thread overview]
Message-ID: <20260622184100.33490-1-manibharadwajcr@gmail.com> (raw)
Move the return statement in ia_css_anr_dump() to its own line
to fix the following checkpatch error:
ERROR: trailing statements should be on next line
No functional change.
Changes in v3:
- Fix subject prefix: add missing 'media:' subsystem tag
per Media CI bot feedback.
Signed-off-by: Mani Bharadwaj <manibharadwajcr@gmail.com>
---
.../atomisp/pci/isp/kernels/anr/anr_1.0/ia_css_anr.host.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/pci/isp/kernels/anr/anr_1.0/ia_css_anr.host.c b/drivers/staging/media/atomisp/pci/isp/kernels/anr/anr_1.0/ia_css_anr.host.c
index 899d56623..fd50a20ac 100644
--- a/drivers/staging/media/atomisp/pci/isp/kernels/anr/anr_1.0/ia_css_anr.host.c
+++ b/drivers/staging/media/atomisp/pci/isp/kernels/anr/anr_1.0/ia_css_anr.host.c
@@ -36,7 +36,8 @@ ia_css_anr_dump(
const struct sh_css_isp_anr_params *anr,
unsigned int level)
{
- if (!anr) return;
+ if (!anr)
+ return;
ia_css_debug_dtrace(level, "Advance Noise Reduction:\n");
ia_css_debug_dtrace(level, "\t%-32s = %d\n",
"anr_threshold", anr->threshold);
--
2.54.0
next reply other threads:[~2026-06-22 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 18:41 Mani Bharadwaj [this message]
2026-06-23 9:26 ` [PATCH v3] staging: media: atomisp: anr: move trailing statement to its own line 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=20260622184100.33490-1-manibharadwajcr@gmail.com \
--to=manibharadwajcr@gmail.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