From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Kibaek Yoo" <psykibaek@gmail.com>, <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>
Subject: Re: [PATCH v2] staging: nvec: fix block comment style in nvec_interrupt()
Date: Mon, 23 Feb 2026 23:21:13 -0600 [thread overview]
Message-ID: <DGMXUA7MV0MK.1PY2AL3PHA7KF@gmail.com> (raw)
In-Reply-To: <20260224044946.54022-1-psykibaek@gmail.com>
On Mon Feb 23, 2026 at 10:49 PM CST, Kibaek Yoo wrote:
> Fix multi-line block comment to use the preferred kernel comment style
> with leading asterisks on each line and a trailing */ on a separate
> line, as reported by checkpatch.pl.
>
> Signed-off-by: Kibaek Yoo <psykibaek@gmail.com>
> ---
LGTM.
Reviewed-by: Ethan Tidmore <ethantidmore06@gmail.com>
Thanks,
ET
prev parent reply other threads:[~2026-02-24 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 14:31 [PATCH] staging: nvec: fix block comment style in nvec_interrupt() yykkibbb
2026-02-23 14:39 ` Greg KH
2026-02-24 4:49 ` [PATCH v2] " Kibaek Yoo
2026-02-24 5:21 ` Ethan Tidmore [this message]
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=DGMXUA7MV0MK.1PY2AL3PHA7KF@gmail.com \
--to=ethantidmore06@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 \
--cc=psykibaek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox