mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gregory Price (Meta)" <gourry@gourry.net>
To: shao.mingyin@zte.com.cn
Cc: ljs@kernel.org, akpm@linux-foundation.org, liam@infradead.org,
	 linux-mm@kvack.org, vbabka@kernel.org, jannh@google.com,
	pfalcato@suse.de,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vma: restore VMA iterator on full-range merge failure
Date: Sat, 14 Nov 2026 14:47:17 -0500	[thread overview]
Message-ID: <179468563735.482102.182237761852902643.b4-reply@b4> (raw)
In-Reply-To: <20261115025832904-wsPy8LPoyIcDJ6FMU1_H@zte.com.cn>

On 2026-11-15 02:58 +0800, shao.mingyin@zte.com.cn wrote:
> 
> I would like to learn from the technical feedback and improve the
> quality of my contributions. Thank you for any further guidance you
> are willing to offer, and again, sorry for the interruption.
> 

It's a matter of triage, attention, and respect for people's time.

If a bug is unreachable or so low impact that it has no appreciable
effect on in-tree code, mass-driveby submissions take maintainer
attention away from critical issues. That is a net-negative.

Exporting this triage (mental load) to maintainers creates a strain
on the humans in the loop.

By the time the patch / report is read, the damage is done.

Even reading your patch message, it's unclear to me what the iterator
position being off even means.  What visible effect does this have?
(None, it's not even obviously a bug).

You may ask why not pass the patch to an LLM to help automate that,
but then you are externalizing the token cost (and someone still has
to read the output).

This is not intended to put you down, just to illustrate the frustration
that these kinds of submissions is causing.

-- 
~Gregory


  reply	other threads:[~2026-11-14 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 16:46 shao.mingyin
2026-11-14 17:14 ` Lorenzo Stoakes (ARM)
2026-11-14 18:58   ` shao.mingyin
2026-11-14 19:47     ` Gregory Price (Meta) [this message]
2026-11-14 21:15       ` shao.mingyin

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=179468563735.482102.182237761852902643.b4-reply@b4 \
    --to=gourry@gourry.net \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=pfalcato@suse.de \
    --cc=shao.mingyin@zte.com.cn \
    --cc=vbabka@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

all inboxes | Powered by JetHome®