From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@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>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] scheduler updates for v5.19
Date: Wed, 25 May 2022 13:47:23 +0200 [thread overview]
Message-ID: <Yo4XSzZp68hGAZnF@gmail.com> (raw)
In-Reply-To: <20220524140035.GL1790663@paulmck-ThinkPad-P17-Gen-1>
* Paul E. McKenney <paulmck@kernel.org> wrote:
> > > 23 files changed, 266 insertions(+), 331 deletions(-)
> >
> > Note that the above is a v5.18 based shortlog and diffstat, but because the
> > RCU tree deep-merged one of the scheduler commits that introduced better,
> > Kconfig-invariant preemption model accessors:
> >
> > cfe43f478b79 preempt/dynamic: Introduce preemption model accessors
>
> Ah, this one:
>
> cfe43f478b79 ("preempt/dynamic: Introduce preemption model accessors")
>
> Please accept my apologies for the disruption. This commit was needed
> to be able to properly handle CONFIG_PREEMPT_DYNAMIC=y kernels booting
> with preempt=none or preempt=voluntary. But I should have called this
> out in my pull request, and failed to do so. Again, please accept my
> apologies for the disruption.
No problem - Linus pulled the scheduler tree and all is good now I think.
Thanks,
Ingo
next prev parent reply other threads:[~2022-05-25 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 17:02 [GIT PULL] scheduler updates for v5.19 Ingo Molnar
2022-05-24 5:49 ` Ingo Molnar
2022-05-24 14:00 ` Paul E. McKenney
2022-05-25 11:47 ` Ingo Molnar [this message]
2022-05-24 19:53 ` pr-tracker-bot
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=Yo4XSzZp68hGAZnF@gmail.com \
--to=mingo@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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