From: Alexandru Hossu <hossu.alexandru@gmail.com>
To: marvin24@gmx.de
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH] staging: nvec: fix block comment style in nvec.c
Date: Wed, 4 Mar 2026 11:55:04 +0100 [thread overview]
Message-ID: <4e5c94d5-882b-451a-9619-fe4b4783f1a3@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 140 bytes --]
Fix block comment style in nvec.c to comply with kernel
coding style guidelines.
Signed-off-by: Alexandru Hossu <hossu.alexandru@gmail.com>
[-- Attachment #2: 0001-staging-nvec-fix-block-comment-style-in-nvec.c.patch --]
[-- Type: text/plain, Size: 902 bytes --]
From 2bffc2680eeab8d0f4a07c1749a60bc1c034483e Mon Sep 17 00:00:00 2001
From: Alexandru Hossu <hossu.alexandru@gmail.com>
Date: Wed, 4 Mar 2026 11:20:47 +0100
Subject: [PATCH] staging: nvec: fix block comment style in nvec.c
Signed-off-by: Alexandru Hossu <hossu.alexandru@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.43.0
next reply other threads:[~2026-03-04 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 10:55 Alexandru Hossu [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 13:07 [PATCH] staging: nvec: fix block comment style in nvec.c Alexandru Hossu
2026-03-04 14:47 ` Greg KH
2026-03-04 19:18 Oskar Ray-Frayssinet
2026-03-09 16:40 ` Greg KH
2026-03-17 12:01 Martin Bojorquez
2026-03-18 15:32 ` Greg KH
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=4e5c94d5-882b-451a-9619-fe4b4783f1a3@gmail.com \
--to=hossu.alexandru@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.