From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, imx@lists.linux.dev,
Frank Li <Frank.Li@nxp.com>,
Griffin Kroah-Hartman <griffin@kroah.com>,
stable@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: fl1-edma: Add error handling for devm_kasprintf
Date: Wed, 15 Jul 2026 08:35:09 +0200 [thread overview]
Message-ID: <2026071505-kosher-showroom-1e1e@gregkh> (raw)
In-Reply-To: <ac9b775f-7a3e-4bf3-9f31-058039a7dd93@web.de>
On Wed, Jul 15, 2026 at 08:11:09AM +0200, Markus Elfring wrote:
> >>>> Add error handling statement to fls_edma3_irq_init() for the
> >>>> devm_kasprintf call.
> >> …
> >>> Applied, thanks!
> >>>
> >>> [1/1] dmaengine: fl1-edma: Add error handling for devm_kasprintf
> >>> commit: bf1af4dfdc017dfe989c0dbcf0e608dc95f1d2cb
> >>
> >> Frank Li requested a corrected patch subject.
> >
> > Which was done while applying
> > bf1af4dfdc01 dmaengine: fsl-edma: Add error handling for devm_kasprintf
> I find it unfortunate that an improvable text was mentioned in the notification.
>
> Did different development opinions remain if all involved function names
> should usually be marked with parentheses?
>
> Regards,
> Markus
Hi,
This is the semi-friendly patch-bot of Greg Kroah-Hartman.
Markus, you seem to have sent a nonsensical or otherwise pointless
review comment to a patch submission on a Linux kernel developer mailing
list. I strongly suggest that you not do this anymore. Please do not
bother developers who are actively working to produce patches and
features with comments that, in the end, are a waste of time.
Patch submitter, please ignore Markus's suggestion; you do not need to
follow it at all. The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and
inability to adapt to feedback. Please feel free to also ignore emails
from them.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2026-07-15 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:57 [PATCH] dmaengine: fl1-edma: Add error handling for devm_kasprintf Greg Kroah-Hartman
2026-07-06 15:10 ` sashiko-bot
2026-07-06 16:31 ` Frank Li
2026-07-14 12:36 ` Vinod Koul
2026-07-14 15:01 ` Markus Elfring
2026-07-15 6:00 ` Vinod Koul
2026-07-15 6:11 ` Markus Elfring
2026-07-15 6:35 ` Greg Kroah-Hartman [this message]
2026-07-14 15:58 ` Markus Elfring
2026-07-14 16:05 ` Greg Kroah-Hartman
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=2026071505-kosher-showroom-1e1e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Frank.Li@nxp.com \
--cc=Markus.Elfring@web.de \
--cc=dmaengine@vger.kernel.org \
--cc=griffin@kroah.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=vkoul@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