From: Lance Yang <lance.yang@linux.dev>
To: atomlin@atomlin.com
Cc: akpm@linux-foundation.org, 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,
Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH v7 0/2] hung_task: Improve warning budget handling and task reporting
Date: Wed, 5 Aug 2026 00:30:15 +0800 [thread overview]
Message-ID: <20260804163015.73614-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260804155406.254810-1-atomlin@atomlin.com>
On Tue, Aug 04, 2026 at 11:54:04AM -0400, Aaron Tomlin wrote:
[...]
A couple of things look off ...
>Petr Mladek (2):
> hung_task: Reset warning budget when problem gets resolved
> hung_task: Always print basic hung task info header
The authorship is still wrong ... Petr is listed in the in-body From:,
but there is no matching Signed-off-by from him. That in-body From:
should be dropped :)
All patch changelogs read AI-ish: lots of words, but unclear on what
changes and why ...
Cheers, Lance
next prev parent reply other threads:[~2026-08-04 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 15:54 [PATCH v7 0/2] hung_task: Improve warning budget handling and task reporting Aaron Tomlin
2026-08-04 15:54 ` [PATCH v7 1/2] hung_task: Reset warning budget when problem gets resolved Aaron Tomlin
2026-08-04 16:40 ` Lance Yang
2026-08-04 17:35 ` Aaron Tomlin
2026-08-04 15:54 ` [PATCH v7 2/2] hung_task: Always print basic hung task info header Aaron Tomlin
2026-08-04 16:42 ` Lance Yang
2026-08-04 17:36 ` Aaron Tomlin
2026-08-04 16:30 ` Lance Yang [this message]
2026-08-04 17:32 ` [PATCH v7 0/2] hung_task: Improve warning budget handling and task reporting Aaron Tomlin
2026-08-05 1:48 ` Lance Yang
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=20260804163015.73614-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox