From: Richard Weinberger <richard@nod.at>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-stm32 <linux-stm32@st-md-mailman.stormreply.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
alexandre torgue <alexandre.torgue@foss.st.com>,
mcoquelin stm32 <mcoquelin.stm32@gmail.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
wanqian10@huawei.com, Yang Liu <young.liuyang@huawei.com>,
chengzhihao1 <chengzhihao1@huawei.com>,
Liyuan Pang <pangliyuan1@huawei.com>
Subject: Re: [v2] ubi: fastmap: fix ubi->fm memory leak
Date: Fri, 7 Nov 2025 20:23:14 +0100 (CET) [thread overview]
Message-ID: <79797154.158914.1762543394141.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <14f5091f-b647-40c9-9c32-6a705c2d6c37@web.de>
----- Ursprüngliche Mail -----
> Von: "Markus Elfring" <Markus.Elfring@web.de>
>> > You may occasionally put more than 60 characters into text lines
>> > of such a change description.
>> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc4#n658
>
>> Feel free to ignore everything Markus says.
>
> Does your feedback indicate then also that Linux development process
> documentation may be overlooked any more?
The only reason why you are not on my kill file is that I can protect newbies from you.
To quote GregKH[0]:
> 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,
//richard
[0] https://lore.kernel.org/lkml/2025110516-cubical-drowsily-7acd@gregkh/
prev parent reply other threads:[~2025-11-07 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 10:00 [PATCH v2] ubi: fastmap: fix ubi->fm memory leak Liyuan Pang
2025-11-07 12:13 ` Markus Elfring
[not found] ` <DF8B15D4-4819-47E6-9BB0-268AD0204C86@nod.at>
2025-11-07 18:25 ` [v2] " Markus Elfring
2025-11-07 19:23 ` Richard Weinberger [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=79797154.158914.1762543394141.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=Markus.Elfring@web.de \
--cc=alexandre.torgue@foss.st.com \
--cc=chengzhihao1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=pangliyuan1@huawei.com \
--cc=vigneshr@ti.com \
--cc=wanqian10@huawei.com \
--cc=young.liuyang@huawei.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