From: Greg KH <gregkh@linuxfoundation.org>
To: Afkari Zergaw <afkarizergaw12@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
Date: Mon, 9 Mar 2026 17:28:32 +0100 [thread overview]
Message-ID: <2026030927-egging-nearness-aebf@gregkh> (raw)
In-Reply-To: <20260302014015.3853-1-afkarizergaw12@gmail.com>
On Mon, Mar 02, 2026 at 01:40:15AM +0000, Afkari Zergaw wrote:
> Convert a block comment in nvec.c to follow the kernel block
> comment style where subsequent lines start with '*'.
>
> Signed-off-by: Afkari Zergaw <afkarizergaw12@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.43.0
>
>
Does not apply to my tree :(
next prev parent reply other threads:[~2026-03-09 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 1:40 [PATCH] staging: nvec: fix block comment style Afkari Zergaw
2026-03-09 16:28 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 5:47 Avon-Hermit
2026-03-06 5:01 ` Avon Hermit
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=2026030927-egging-nearness-aebf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=afkarizergaw12@gmail.com \
--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