public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <jstultz@google.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	Suleiman Souhlal <suleiman@google.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	kernel-team@android.com
Subject: Re: [PATCH] [RFC]: sched/deadline: Avoid double enqueue_pushable_dl_task() warning
Date: Sat, 7 Mar 2026 13:55:30 +0100	[thread overview]
Message-ID: <20260307125530.GW606826@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CANDhNCqJou9KmGjhX5-Q_iFKz9pR1Dgab09zmJEq=emUkkTzTw@mail.gmail.com>

On Fri, Mar 06, 2026 at 03:45:12PM -0800, John Stultz wrote:
> With those two tweaks it has been running ok in testing.
> 
> I've also split out your cleanups into a separate patch just so the
> functional change is easier to review.
> 
> Since this is proxy-exec specific, I'll include these both in my next
> submission of the donor-migration logic.
> 
> Let me know if you think I'm still missing anything subtle here.

Sounds about right.

Thanks!

      reply	other threads:[~2026-03-07 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 19:41 [PATCH] [RFC]: sched/deadline: Avoid double enqueue_pushable_dl_task() warning John Stultz
2026-03-04  7:06 ` Juri Lelli
2026-03-04  9:51   ` Peter Zijlstra
2026-03-04 13:59     ` Juri Lelli
2026-03-05  2:35     ` John Stultz
2026-03-06 23:45     ` John Stultz
2026-03-07 12:55       ` Peter Zijlstra [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=20260307125530.GW606826@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kernel-team@android.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=suleiman@google.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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