From: Lance Yang <lance.yang@linux.dev>
To: atomlin@atomlin.com
Cc: akpm@linux-foundation.org, lance.yang@linux.dev,
mhiramat@kernel.org, pmladek@suse.com,
linux-kernel@vger.kernel.org, david.laight.linux@gmail.com,
neelx@suse.com, sean@ashe.io, chjohnst@gmail.com, steve@abita.co,
mproche@gmail.com, nick.lange@gmail.com
Subject: Re: [PATCH v4] hung_task: Deduplicate identical hang reports using explicit blocker tracking
Date: Sun, 28 Jun 2026 12:47:50 +0800 [thread overview]
Message-ID: <20260628044750.32878-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260627205733.90983-1-atomlin@atomlin.com>
Sorry, but NACK from me.
Aaron, please slow down a bit here!
I already said in v2 that the discussion didn't feel settled, and asked
you to wait before another spin. v3 didn't settle it either ...
Replying to comments is *not* the same as settling review ... If any
reviewer/maintainer still doesn't agree this should go in, please read
the room a bit and stop spining new versions until we agree on the next
move.
If v3 didn't settle it (i.e. we didn't agree on the next move), please
don't just spin v4. Step back first: what real problem does this solve?
If this isn't really a real-world problem at all, why keep spinning it?
At that point it starts looking less like review and more like patch
churn. That usually doesnt land, it just *burns* reviewer time ...
I'd rather spend review time on patches where we at least agree the
problem is real. I assume you'd prefer that too :)
So yeah, still a NACK from me. If new versions keep coming before the
discussion settles, I'll keep NACKing them ...
Thanks, Lance
prev parent reply other threads:[~2026-06-28 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 20:57 [PATCH v4] hung_task: Deduplicate identical hang reports using explicit blocker tracking Aaron Tomlin
2026-06-28 4:47 ` Lance Yang [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=20260628044750.32878-1-lance.yang@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=chjohnst@gmail.com \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mproche@gmail.com \
--cc=neelx@suse.com \
--cc=nick.lange@gmail.com \
--cc=pmladek@suse.com \
--cc=sean@ashe.io \
--cc=steve@abita.co \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.