linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Liu Xinpeng <liuxp11@chinatelecom.cn>,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	juri.lelli@redhat.com, zhouchengming@bytedance.com
Subject: Re: [PATCH 1/2] psi: Remove repeated verbose comment
Date: Tue, 9 Nov 2021 10:14:54 +0100	[thread overview]
Message-ID: <YYo8DsWX///Qgnqu@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <YYQPL4exZUP2eruI@cmpxchg.org>

On Thu, Nov 04, 2021 at 12:49:51PM -0400, Johannes Weiner wrote:
> On Mon, Oct 25, 2021 at 11:46:25AM +0800, Liu Xinpeng wrote:
> > Comment in function psi_task_switch,there are two same lines.
> > ...
> > * runtime state, the cgroup that contains both tasks
> > * runtime state, the cgroup that contains both tasks
> > ...
> > 
> > Signed-off-by: Liu Xinpeng <liuxp11@chinatelecom.cn>
> 
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> 
> Peter, could you please take this through -tip?

Sure, lemme figure out the b4 incantation to grab these patches since
the originals didn't make it to my inbox. They should show up in
tip/sched/core after -rc1 or so if I get the incantation right :-)

  reply	other threads:[~2021-11-09  9:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25  3:46 [PATCH 1/2] psi: Remove repeated verbose comment Liu Xinpeng
2021-10-25  3:46 ` [PATCH 2/2] psi: Add a missing SPDX license header Liu Xinpeng
2021-11-04 16:50   ` Johannes Weiner
2021-11-17 14:00   ` [tip: sched/core] " tip-bot2 for Liu Xinpeng
2021-11-04 16:49 ` [PATCH 1/2] psi: Remove repeated verbose comment Johannes Weiner
2021-11-09  9:14   ` Peter Zijlstra [this message]
2021-11-17 14:00 ` [tip: sched/core] " tip-bot2 for Liu Xinpeng

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=YYo8DsWX///Qgnqu@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuxp11@chinatelecom.cn \
    --cc=mingo@redhat.com \
    --cc=zhouchengming@bytedance.com \
    /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;
as well as URLs for NNTP newsgroup(s).