All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bojorquez <dihed1973@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,
	Martin Bojorquez <dihed1973@gmail.com>
Subject: [PATCH] staging: nvec: fix block comment style in nvec.c
Date: Tue, 17 Mar 2026 05:01:14 -0700	[thread overview]
Message-ID: <20260317120114.39057-1-dihed1973@gmail.com> (raw)

Block comments should use * on subsequent lines and a trailing */
on a separate line, as required by the kernel coding style.

Signed-off-by: Martin Bojorquez <dihed1973@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 e9af66a08448..0e655f79ea4a 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.53.0


             reply	other threads:[~2026-03-17 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 12:01 Martin Bojorquez [this message]
2026-03-18 15:32 ` [PATCH] staging: nvec: fix block comment style in nvec.c Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2026-03-04 19:18 Oskar Ray-Frayssinet
2026-03-09 16:40 ` Greg KH
2026-03-04 13:07 Alexandru Hossu
2026-03-04 14:47 ` Greg KH
2026-03-04 10:55 Alexandru Hossu

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=20260317120114.39057-1-dihed1973@gmail.com \
    --to=dihed1973@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 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.