mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <yang.yang29@zte.com.cn>
To: <wang.yaxin@zte.com.cn>, <fan.yu9@zte.com.cn>
Cc: <krzk@kernel.org>, <jiang.kun2@zte.com.cn>,
	<akpm@linux-foundation.org>, <xu.xin16@zte.com.cn>,
	<bbonev@devuan.org>, <linux-kernel@vger.kernel.org>,
	<bsingharora@gmail.com>
Subject: Re: [PATCH linux next] MAINTAINERS: add maintainers for delaytop
Date: Tue, 22 Jul 2025 22:56:17 +0800 (CST)	[thread overview]
Message-ID: <20250722225617123Fj3T0Py6UEGIXmSx1VH7s@zte.com.cn> (raw)
In-Reply-To: <20250722165841838ou4ZoIujZCCgIG2HAu1T8@zte.com.cn>

> which is highly beneficial for improving system performance. Wang Yaxin
> and her colleague Fan Yu focus on locating system delay issues. To promote
> the thriving development of delaytop, we hope to serve as maintainers to
> continuously improve it, aiming to provide a more effective solution for
> system latency issues in the future.
I'm pleased to see young colleagues contributing multiple patches in the field of
delay observation and aspiring to become maintainers of new tools. With more
and more latency-sensitive devices running Linux, such as communication
equipment and intelligent vehicles, I believe delay observation is a promising
area, and thus delaytop has good potential for application. On the other hand,
the tool is still somewhat simple, and I have already replied with some suggestions
—I would feel happy if you adopt them. I thingk becoming a maintainer means
passion and responsibility, hope you will keep moving forward. Best of luck!

Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>

      reply	other threads:[~2025-07-22 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21  1:40 jiang.kun2
2025-07-21  6:56 ` Krzysztof Kozlowski
2025-07-22  0:52   ` Andrew Morton
2025-07-22  8:58   ` wang.yaxin
2025-07-22 14:56     ` yang.yang29 [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=20250722225617123Fj3T0Py6UEGIXmSx1VH7s@zte.com.cn \
    --to=yang.yang29@zte.com.cn \
    --cc=akpm@linux-foundation.org \
    --cc=bbonev@devuan.org \
    --cc=bsingharora@gmail.com \
    --cc=fan.yu9@zte.com.cn \
    --cc=jiang.kun2@zte.com.cn \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wang.yaxin@zte.com.cn \
    --cc=xu.xin16@zte.com.cn \
    /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®