All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Oskar Ray-Frayssinet <rayfraytech@gmail.com>
Cc: marvin24@gmx.de, linux-staging@lists.linux.dev,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: nvec: fix block comment style in nvec.c
Date: Mon, 9 Mar 2026 17:40:43 +0100	[thread overview]
Message-ID: <2026030929-uncheck-reclining-315b@gregkh> (raw)
In-Reply-To: <20260304191853.4500-1-rayfraytech@gmail.com>

On Wed, Mar 04, 2026 at 08:18:53PM +0100, Oskar Ray-Frayssinet wrote:
> Fix block comment formatting to use * on subsequent lines
> and */ on a separate line as required by kernel coding style.
> 
> Signed-off-by: Oskar Ray-Frayssinet <rayfraytech@gmail.com>
> ---
>  drivers/staging/nvec/nvec.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
> index e9af66a08448..ee2715df3b48 100644
> --- a/drivers/staging/nvec/nvec.c
> +++ b/drivers/staging/nvec/nvec.c
> @@ -646,7 +646,7 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
>  			nvec->state = 2;
>  		}
>  		break;
> -	case 2:		/* first byte after command */
> +	case 2:		/* First byte after command */

THis change is not what you document above as being changed :(


  reply	other threads:[~2026-03-09 16:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 19:18 [PATCH] staging: nvec: fix block comment style in nvec.c Oskar Ray-Frayssinet
2026-03-09 16:40 ` Greg KH [this message]
2026-03-09 22:07   ` [PATCH v3] " Oskar Ray-Frayssinet
2026-03-18 14:59     ` Greg KH
2026-03-18 21:46       ` Oskar Ray-Frayssinet
2026-03-28  0:21       ` Thierry Reding
2026-03-30 14:29         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2026-03-17 12:01 [PATCH] " Martin Bojorquez
2026-03-18 15:32 ` 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=2026030929-uncheck-reclining-315b@gregkh \
    --to=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 \
    --cc=rayfraytech@gmail.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 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.