From: Avon Hermit <avon.hermit@gmail.com>
To: Marc Dietrich <marvin24@gmx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
ac100@lists.launchpad.net, linux-tegra@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: nvec: fix block comment style
Date: Fri, 6 Mar 2026 13:01:48 +0800 [thread overview]
Message-ID: <aapfvNobk8atPbyY@general> (raw)
In-Reply-To: <20260304054727.70113-1-avon.hermit@gmail.com>
Hi,
Sorry, I didn't notice the earlier patch.
Please ignore this one.
Thanks,
Avon
On Wed, Mar 04, 2026 at 01:47:20PM +0800, Avon-Hermit wrote:
> Convert a block comment describing the AP20 hardware bug workaround
> to the preferred kernel block comment format.
>
> This change only adjusts the comment style and does not modify the
> behavior of the driver.
>
> Signed-off-by: Avon-Hermit <avon.hermit@gmail.com>
> ---
> drivers/staging/nvec/nvec.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
> index e9af66a08448..736f11942174 100644
> --- a/drivers/staging/nvec/nvec.c
> +++ b/drivers/staging/nvec/nvec.c
> @@ -659,8 +659,9 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
> nvec_tx_set(nvec);
> to_send = nvec->tx->data[0];
> nvec->tx->pos = 1;
> - /* delay ACK due to AP20 HW Bug
> - do not replace by usleep_range */
> + /*
> + * Delay ACK due to AP20 HW Bug; do not replace by usleep_range.
> + */
> udelay(33);
> } else if (status == (I2C_SL_IRQ)) {
> nvec->rx->data[1] = received;
> --
> 2.47.3
>
next prev parent reply other threads:[~2026-03-06 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 5:47 [PATCH] staging: nvec: fix block comment style Avon-Hermit
2026-03-06 5:01 ` Avon Hermit [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-02 1:40 Afkari Zergaw
2026-03-09 16:28 ` Greg KH
2026-02-07 18:25 claude-bot
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=aapfvNobk8atPbyY@general \
--to=avon.hermit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox