From: Serban-Pascu Robert <robyserbanpascu06@gmail.com>
To: hansg@kernel.org, mchehab@kernel.org
Cc: andy@kernel.org, sakari.ailus@linux.intel.com,
gregkh@linuxfoundation.org, daniel.baluta@nxp.com,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Serban-Pascu Robert <robyserbanpascu06@gmail.com>
Subject: [PATCH v3 3/4] staging: media: atomisp: reformat block comments
Date: Sun, 29 Mar 2026 21:48:09 +0300 [thread overview]
Message-ID: <20260329184810.455285-4-robyserbanpascu06@gmail.com> (raw)
In-Reply-To: <20260329184810.455285-1-robyserbanpascu06@gmail.com>
Add missing asterisks to block comments to conform with the
standard Linux kernel comment style.
Signed-off-by: Serban-Pascu Robert <robyserbanpascu06@gmail.com>
---
drivers/staging/media/atomisp/pci/system_global.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/system_global.h b/drivers/staging/media/atomisp/pci/system_global.h
index 6420436d88f7..c65a5be8445a 100644
--- a/drivers/staging/media/atomisp/pci/system_global.h
+++ b/drivers/staging/media/atomisp/pci/system_global.h
@@ -100,8 +100,9 @@ typedef enum {
N_GDC_ID
} gdc_ID_t;
-/* this extra define is needed because we want to use it also
- in the preprocessor, and that doesn't work with enums.
+/*
+ * this extra define is needed because we want to use it also
+ * in the preprocessor, and that doesn't work with enums.
*/
#define N_GDC_ID_CPP 2
--
2.43.0
next prev parent reply other threads:[~2026-03-29 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 18:48 [PATCH v3 0/4] Serban-Pascu Robert
2026-03-29 18:48 ` [PATCH v3 1/4] staging: media: atomisp: fix SPDX license identifier style Serban-Pascu Robert
2026-03-29 18:48 ` [PATCH v3 2/4] staging: media: atomisp: fix typo Serban-Pascu Robert
2026-03-29 18:48 ` Serban-Pascu Robert [this message]
2026-03-29 18:48 ` [PATCH v3 4/4] staging: media: atomisp: remove redundant blank lines Serban-Pascu Robert
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=20260329184810.455285-4-robyserbanpascu06@gmail.com \
--to=robyserbanpascu06@gmail.com \
--cc=andy@kernel.org \
--cc=daniel.baluta@nxp.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