mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Parri <parri.andrea@gmail.com>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	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>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <clrkwllms@kernel.org>,
	Aaron Tomlin <atomlin@atomlin.com>,
	linux-rt-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/deadline: Fix spurious -EPERM for migration-disabled tasks
Date: Tue,  3 Nov 2026 14:20:13 +0100	[thread overview]
Message-ID: <20261103132022.4004-1-parri.andrea@gmail.com> (raw)
In-Reply-To: <aumIRjQS2M0wWlVq@jlelli-thinkpadt14gen4.remote.csb>

On Tue, Nov 03, 2026 at 08:07:50AM +0100, Juri Lelli wrote:

[...]

> The fix makes sense to me.
>
> Acked-by: Juri Lelli <juri.lelli@redhat.com>

Thanks!

> I only wonder if we want the reproducer in the changelog. An alternative
> might be to move it to https://github.com/jlelli/sched-deadline-tests
> where I keep the rest of SCHED_DEADLINE tests. I can probably do that if
> you agree and prefer.

Fine with me, please go ahead, for this one and for the cpuset_mutex
one too, if it fits there.  If you'd like a v2 of both, with the
programs replaced by a link and the tags collected, just let me know.

Thanks,
  Andrea

  reply	other threads:[~2026-11-03 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 13:54 Andrea Parri
2026-11-02 14:45 ` Aaron Tomlin
2026-11-02 15:14   ` Andrea Parri
2026-11-02 17:00     ` Aaron Tomlin
2026-11-03  7:07 ` Juri Lelli
2026-11-03 13:20   ` Andrea Parri [this message]
2026-11-03  8:11 ` Sebastian Andrzej Siewior
2026-11-03 15:34   ` Andrea Parri

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=20261103132022.4004-1-parri.andrea@gmail.com \
    --to=parri.andrea@gmail.com \
    --cc=atomlin@atomlin.com \
    --cc=bigeasy@linutronix.de \
    --cc=bsegall@google.com \
    --cc=clrkwllms@kernel.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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
all inboxes | Powered by JetHome®