From: "Michal Koutný" <mkoutny@suse.com>
To: Shaojie Sun <sunshaojie@kylinos.cn>
Cc: tj@kernel.org, cgroups@vger.kernel.org, corbet@lwn.net,
cui.tao@linux.dev, hannes@cmpxchg.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: PING [PATCH v3] cgroup/cpu: document cpu.stat.local and clarify cpu.stat behavior
Date: Mon, 20 Jul 2026 15:16:28 +0200 [thread overview]
Message-ID: <al4fAmim8rdPCKlB@localhost.localdomain> (raw)
In-Reply-To: <20260720100941.230825-1-sunshaojie@kylinos.cn>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
Hi.
On Mon, Jul 20, 2026 at 06:09:41PM +0800, Shaojie Sun <sunshaojie@kylinos.cn> wrote:
> Just a gentle ping on this documentation patch. It received an
> Acked-by from Michal about three weeks ago. Any chance this could be
> picked up for the next merge window, or is there anything else needed
> from my side?
>
> The commit in linux-next is: 171569f8ee6724a4113a0100fea6ff83d9b70c6a
That's how linux-next works [1]:
| The linux-next tree is, by design, a snapshot of what the mainline is
| expected to look like after the next merge window closes.
So that patch is currently heading for-7.3.
HTH,
Michal
[1] https://www.kernel.org/doc/html/latest/process/2.Process.html#next-trees
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]
prev parent reply other threads:[~2026-07-20 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 13:07 [PATCH] cgroup/cpu: document cpu.stat.local Sun Shaojie
2026-06-25 14:05 ` Tao Cui
2026-06-26 1:09 ` [PATCH v2] " Sun Shaojie
2026-06-26 16:24 ` Michal Koutný
2026-06-29 6:06 ` [PATCH v3] cgroup/cpu: document cpu.stat.local and clarify cpu.stat behavior Sun Shaojie
2026-06-29 13:49 ` Michal Koutný
2026-06-29 18:55 ` Tejun Heo
2026-07-20 10:09 ` PING " Shaojie Sun
2026-07-20 13:16 ` Michal Koutný [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=al4fAmim8rdPCKlB@localhost.localdomain \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=cui.tao@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=sunshaojie@kylinos.cn \
--cc=tj@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