mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Eric_Terminal <ericterminal@gmail.com>
Cc: shubhrajyoti.datta@amd.com, linux-kernel@vger.kernel.org,
	tony.luck@intel.com, linux-edac@vger.kernel.org
Subject: Re: [PATCH] EDAC/versalnet: Fix resource leaks and NULL derefs in init_versalnet()
Date: Mon, 23 Feb 2026 10:40:14 +0000	[thread overview]
Message-ID: <A0F02AA6-0ADE-4C05-92A8-240C3F538066@alien8.de> (raw)
In-Reply-To: <CAKNPVZAeEWB6Q0VRB7099s4xtLZXq9gqDnrfeYHkfFv9pEjaag@mail.gmail.com>

On February 23, 2026 10:08:02 AM UTC, Eric_Terminal <ericterminal@gmail.com> wrote:
>To explain the "way too polished English": English is not my native
>language. Because I want to show proper respect to the kernel
>community, I relied on translation and grammar tools to make sure my
>replies were polite and appropriate. That is why the text might look
>artificially perfect.

Such quality must come from a LLM-like tool...

>As for not complaining: I don't know how other submitters do it, but
>as a newcomer, I honestly didn't dare to complain on the mailing list.
>I simply assumed that complaining would leave a bad impression and
>might get my patch rejected. So I just tried my best to read the
>documentation and follow the rules as quickly as possible.

You should never aim for "quickly" but for correctly. Never rush your replies.

>If I were a fully automated AI bot, I probably

So you are using some AI to generate your mails? You should state that in your commit message.

But I'll take a look at your patch first...

-- 
Small device. Typos and formatting crap

  reply	other threads:[~2026-02-23 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-21  7:16 Eric-Terminal
2026-02-22  2:44 ` Borislav Petkov
     [not found]   ` <CAKNPVZA36XvT7R+QWTOTvAeQNA-sZfnG-h5jV3FnKvKOxqiGtA@mail.gmail.com>
     [not found]     ` <FE3C5380-E82B-4EC8-B1C0-16026CEEF8A2@alien8.de>
2026-02-22 10:39       ` Eric-Terminal
2026-02-23 13:47         ` Borislav Petkov
2026-02-23 14:58           ` Eric_Terminal
2026-02-26  6:54             ` Datta, Shubhrajyoti
2026-02-26 11:29               ` [PATCH v2] " Eric-Terminal
2026-02-26 12:59                 ` Borislav Petkov
2026-02-26 16:52                   ` Datta, Shubhrajyoti
2026-02-22 10:48       ` [PATCH] " Eric_Terminal
2026-02-23  8:54         ` Borislav Petkov
2026-02-23 10:08           ` Eric_Terminal
2026-02-23 10:40             ` Borislav Petkov [this message]
2026-02-23 10:52               ` Eric_Terminal

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=A0F02AA6-0ADE-4C05-92A8-240C3F538066@alien8.de \
    --to=bp@alien8.de \
    --cc=ericterminal@gmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shubhrajyoti.datta@amd.com \
    --cc=tony.luck@intel.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

all inboxes | Powered by JetHome®