From: "Hüseyin Can Erdem" <erdemhuseyincan09@gmail.com>
To: marvin24@gmx.de, gregkh@linuxfoundation.org
Cc: ac100@lists.launchpad.net, linux-tegra@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
"Hüseyin Can Erdem" <erdemhuseyincan09@gmail.com>
Subject: [PATCH] staging: nvec: fix block comment formatting
Date: Wed, 18 Mar 2026 20:06:04 +0300 [thread overview]
Message-ID: <20260318170604.10254-1-erdemhuseyincan09@gmail.com> (raw)
The block comment in nvec_interrupt() does not follow the kernel
coding style. Multi-line block comments should have a * at the
beginning of each line, and the closing */ should be on its own
separate line.
Signed-off-by: Hüseyin Can Erdem <erdemhuseyincan09@gmail.com>
---
drivers/staging/nvec/nvec.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
index e9af66a08..0e655f79e 100644
--- a/drivers/staging/nvec/nvec.c
+++ b/drivers/staging/nvec/nvec.c
@@ -660,7 +660,8 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
to_send = nvec->tx->data[0];
nvec->tx->pos = 1;
/* delay ACK due to AP20 HW Bug
- do not replace by usleep_range */
+ * do not replace by usleep_range
+ */
udelay(33);
} else if (status == (I2C_SL_IRQ)) {
nvec->rx->data[1] = received;
--
2.47.3
next reply other threads:[~2026-03-18 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 17:06 Hüseyin Can Erdem [this message]
2026-03-30 15:49 ` [PATCH] staging: nvec: fix block comment formatting Greg KH
-- strict thread matches above, loose matches on Subject: below --
2026-04-11 13:57 [PATCH] staging: nvec: Fix " Shyam Sunder Reddy Padira
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=20260318170604.10254-1-erdemhuseyincan09@gmail.com \
--to=erdemhuseyincan09@gmail.com \
--cc=ac100@lists.launchpad.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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