public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Raczynski <j.raczynski@samsung.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH RESEND net-next] net/sun: Fix multiple typos in comments
Date: Thu, 30 Apr 2026 17:49:39 +0200	[thread overview]
Message-ID: <afN6CpRoH6g2RdoB@AMDC4622.eu.corp.samsungelectronics.net> (raw)
In-Reply-To: <20260430010322.2326574-1-kuba@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On Wed, Apr 29, 2026 at 06:03:22PM -0700, Jakub Kicinski wrote:
> This is an AI-generated review of your patch. The human sending this
> email has considered the AI review valid, or at least plausible.

I should also implement any basic tools or AI to verify my writing skills.
This patch was basically prepared with help of 'typos' script and yet has
errors.
> The "autonogotiation" to "autonegotiation" change looks correct, but
> the neighbouring "in enabled" in the same sentence appears to be a
> leftover grammar slip (should it read "is enabled"?).  Since this
> sentence is already being touched as part of the typo cleanup, would
> it make sense to fix that at the same time?
Probably, no reason to not do that. Might be good to also change double spaces

> Neither "imperical" nor "emperical" is a correct English word; the
> intended word is "empirical".  Was the replacement here meant to be
> "empirical"?
Writing fail. Funny enough, I had someone read/check this before sending and
it slipped.

Will resend whole patch soon.

Regards
Jakub Raczynski

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2026-04-30 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260428102434eucas1p1dcf39fcb439687a062b0e41ffa3f7830@eucas1p1.samsung.com>
2026-04-28 10:17 ` [PATCH RESEND net-next] net/sun: Fix multiple typos in comments Jakub Raczynski
2026-04-30  1:03   ` Jakub Kicinski
2026-04-30 15:49     ` Jakub Raczynski [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=afN6CpRoH6g2RdoB@AMDC4622.eu.corp.samsungelectronics.net \
    --to=j.raczynski@samsung.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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