All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	Zhan Xusheng <zhanxusheng@xiaomi.com>,
	x86@kernel.org
Subject: Re: [tip: sched/urgent] sched/fair: Fix stale comments referring to removed CFS concepts
Date: Tue, 30 Jun 2026 13:33:45 +0200	[thread overview]
Message-ID: <akOpmTkC6EL2O4CK@gmail.com> (raw)
In-Reply-To: <20260630091015.GA651302@noisy.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> wrote:

> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Link: https://patch.msgid.link/20260629030200.3165589-1-zhanxusheng@xiaomi.com
> 
> This is comments, cannot be urgent.

We sometimes make exception for documentation fixes, which this
in a way is, but only when it does not interfere with pending
changes.

Alas it *does* interfere:

> Also generates non-trivial conflicts
> against the patches I just stuck in sched/core. So zapped this commit.

Sounds good, and I've reapplied a conflict-resolved version on top:

  19b7bdc3a155 ("sched/fair: Fix stale comments referring to removed CFS concepts")

Thanks,

	Ingo

  reply	other threads:[~2026-06-30 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29  3:02 [PATCH] sched/fair: Fix stale comments referring to removed CFS concepts Zhan Xusheng
2026-06-29 11:13 ` [tip: sched/urgent] " tip-bot2 for Zhan Xusheng
2026-06-30  9:10   ` Peter Zijlstra
2026-06-30 11:33     ` Ingo Molnar [this message]
2026-06-30 11:32 ` [tip: sched/core] " tip-bot2 for Zhan Xusheng

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=akOpmTkC6EL2O4CK@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    --cc=zhanxusheng@xiaomi.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 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.