[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180324081549.lqqh6w65d4mfyax5@gmail.com>
Date: Sat, 24 Mar 2018 09:15:49 +0100
From: Ingo Molnar <mingo@...nel.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Claudio Scordino <claudio@...dence.eu.com>
Subject: Re: linux-next: manual merge of the tip tree with the pm tree
* Rafael J. Wysocki <rjw@...ysocki.net> wrote:
> On Friday, March 23, 2018 7:09:24 AM CET Ingo Molnar wrote:
> >
> > * Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > > Hi all,
> > >
> > > Today's linux-next merge of the tip tree got a conflict in:
> > >
> > > kernel/sched/cpufreq_schedutil.c
> > >
> > > between commit:
> > >
> > > 0953feed3400 ("cpufreq: schedutil: rate limits for SCHED_DEADLINE")
> >
> > Rafael, could you please send that to the scheduler tree?
>
> You can apply from
>
> https://patchwork.kernel.org/patch/10278127/
>
> and I will drop it from my tree.
>
> Thanks!
Great - Thomas picked it up and it's now in tip:sched/core:
e97a90f7069b: sched/cpufreq: Rate limits for SCHED_DEADLINE
and it should hit -next on Monday.
Thanks,
Ingo
Powered by blists - more mailing lists