Linux kernel staging patches
 help / color / mirror / Atom feed
From: Mohan Sudhandhiram M <mohan86108@gmail.com>
To: Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Mohan Sudhandhiram M <mohan86108@gmail.com>
Subject: [PATCH] staging: media: atomisp: align block comments to match kernel style
Date: Fri, 29 May 2026 21:13:57 +0530	[thread overview]
Message-ID: <20260529154357.18066-1-mohan86108@gmail.com> (raw)

Fix checkpatch.pl warnings regarding block comments that did not align
the '*' on each line. Removed the custom banner formatting and replaced
it with standard kernel block comments to improve readability and comply
with kernel coding guidelines.

Signed-off-by: Mohan Sudhandhiram M <mohan86108@gmail.com>
---
 .../atomisp/pci/runtime/frame/src/frame.c     | 27 +++++++++----------
 1 file changed, 12 insertions(+), 15 deletions(-)

diff --git a/drivers/staging/media/atomisp/pci/runtime/frame/src/frame.c b/drivers/staging/media/atomisp/pci/runtime/frame/src/frame.c
index 8614efc28..66161942b 100644
--- a/drivers/staging/media/atomisp/pci/runtime/frame/src/frame.c
+++ b/drivers/staging/media/atomisp/pci/runtime/frame/src/frame.c
@@ -17,10 +17,9 @@
 
 #define NV12_TILEY_TILE_WIDTH  128
 #define NV12_TILEY_TILE_HEIGHT  32
-
-/**************************************************************************
-**	Static functions declarations
-**************************************************************************/
+/*
+ * Static functions declarations
+ */
 static void frame_init_plane(struct ia_css_frame_plane *plane,
 			     unsigned int width,
 			     unsigned int stride,
@@ -75,11 +74,9 @@ static struct ia_css_frame *frame_create(unsigned int width,
 static unsigned
 ia_css_elems_bytes_from_info(
     const struct ia_css_frame_info *info);
-
-/**************************************************************************
-**	CSS API functions, exposed by ia_css.h
-**************************************************************************/
-
+/*
+ *	CSS API functions, exposed by ia_css.h
+ */
 int ia_css_frame_allocate_from_info(struct ia_css_frame **frame,
 	const struct ia_css_frame_info *info)
 {
@@ -141,9 +138,9 @@ void ia_css_frame_free(struct ia_css_frame *frame)
 	IA_CSS_LEAVE_PRIVATE("void");
 }
 
-/**************************************************************************
-**	Module public functions
-**************************************************************************/
+/*
+ *	Module public functions
+ */
 
 int ia_css_frame_check_info(const struct ia_css_frame_info *info)
 {
@@ -435,9 +432,9 @@ int ia_css_dma_configure_from_info(struct dma_port_config *config,
 	return 0;
 }
 
-/**************************************************************************
-**	Static functions
-**************************************************************************/
+/*
+ *	Static functions
+ */
 
 static void frame_init_plane(struct ia_css_frame_plane *plane,
 			     unsigned int width,
-- 
2.43.0


                 reply	other threads:[~2026-05-29 15:44 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=20260529154357.18066-1-mohan86108@gmail.com \
    --to=mohan86108@gmail.com \
    --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