From: Mahad Ibrahim <mahad.ibrahim.dev@gmail.com>
To: hansg@kernel.org, mchehab@kernel.org, andy@kernel.org
Cc: sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Mahad Ibrahim <mahad.ibrahim.dev@gmail.com>
Subject: [PATCH] media: atomisp: Fix block comment coding style in sh_css_param_shading.c
Date: Thu, 1 Jan 2026 21:41:17 +0500 [thread overview]
Message-ID: <20260101164117.14292-1-mahad.ibrahim.dev@gmail.com> (raw)
Fix checkpatch.pl warnings in sh_css_param_shading.c regarding block
comment formatting.
The warning was:
- Block comments use a trailing */ on a separate line
This change also moves text from the first line of block comments to
subsequent lines to adhere to the standard Linux kernel coding style.
Signed-off-by: Mahad Ibrahim <mahad.ibrahim.dev@gmail.com>
---
.../media/atomisp/pci/sh_css_param_shading.c | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/sh_css_param_shading.c b/drivers/staging/media/atomisp/pci/sh_css_param_shading.c
index 513e272f2fdc..b5e9d11b28a6 100644
--- a/drivers/staging/media/atomisp/pci/sh_css_param_shading.c
+++ b/drivers/staging/media/atomisp/pci/sh_css_param_shading.c
@@ -20,7 +20,8 @@
#include "platform_support.h"
-/* Bilinear interpolation on shading tables:
+/*
+ * Bilinear interpolation on shading tables:
* For each target point T, we calculate the 4 surrounding source points:
* ul (upper left), ur (upper right), ll (lower left) and lr (lower right).
* We then calculate the distances from the T to the source points: x0, x1,
@@ -116,8 +117,10 @@ crop_and_interpolate(unsigned int cropped_width,
*/
ty = out_start_row + i * out_cell_size;
- /* calculate closest source points in shading table and
- make sure they fall within the table */
+ /*
+ * calculate closest source points in shading table and
+ * make sure they fall within the table
+ */
src_y0 = ty / (int)in_cell_size;
if (in_cell_size < out_cell_size)
src_y1 = (ty + out_cell_size) / in_cell_size;
@@ -173,7 +176,8 @@ crop_and_interpolate(unsigned int cropped_width,
dx0 = tx - sx0;
dx1 = sx1 - tx;
divx = sx1 - sx0;
- /* if we're at the edge, we just use the closest
+ /*
+ * if we're at the edge, we just use the closest
* point still in the grid. We make up for the divider
* in this case by setting the distance to
* out_cell_size, since it's actually 0.
@@ -291,8 +295,10 @@ prepare_shading_table(const struct ia_css_shading_table *in_table,
input_width = min(input_width, in_table->sensor_width);
input_height = min(input_height, in_table->sensor_height);
- /* This prepare_shading_table() function is called only in legacy API (not in new API).
- Then, the legacy shading table width and height should be used. */
+ /*
+ * This prepare_shading_table() function is called only in legacy API (not in new API).
+ * Then, the legacy shading table width and height should be used.
+ */
table_width = binary->sctbl_width_per_color;
table_height = binary->sctbl_height;
--
2.47.3
reply other threads:[~2026-01-01 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260101164117.14292-1-mahad.ibrahim.dev@gmail.com \
--to=mahad.ibrahim.dev@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