From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"Guilherme G. Piccoli" <gpiccoli@canonical.com>,
Sasha Levin <sashal@kernel.org>, Ben Segall <bsegall@google.com>,
Ingo Molnar <mingo@redhat.com>, Phil Auld <pauld@redhat.com>,
Tao Zhou <zohooouoto@zoho.com.cn>,
"# v4 . 16+" <stable@vger.kernel.org>,
Gavin Guo <gavin.guo@canonical.com>,
nivedita.singhvi@canonical.com, halves@canonical.com,
Jay Vosburgh <jay.vosburgh@canonical.com>
Subject: Re: FAILED: patch "[PATCH] sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list" failed to apply to 5.4-stable tree
Date: Wed, 2 Dec 2020 10:44:28 +0100 [thread overview]
Message-ID: <20201202094428.GC3040@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKfTPtDTQsaQbB3OrAD5Q=0d5oULu6TD18+WQ1b-S05n46WeyQ@mail.gmail.com>
On Wed, Dec 02, 2020 at 09:21:19AM +0100, Vincent Guittot wrote:
> On Wed, 2 Dec 2020 at 08:49, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Dec 01, 2020 at 12:03:18PM -0300, Guilherme G. Piccoli wrote:
> > > Hey Sasha, sorry to annoy again, but maybe Peter is very busy - wouldn't
> > > be possible maybe to get that merged after a review from Ben or Ingo? I
> > > see them in the MAINTAINERS file, specially Ben as CONFIG_CFS_BANDWIDTH
> > > maintainer.
> > >
> > > I understand the confidence in this patch is relatively high, since it's
> > > a backport from the author, right?
> >
> > I still want to see an ack from the maintainer please.
>
> SCHEDULER
> M: Vincent Guittot <vincent.guittot@linaro.org> (SCHED_NORMAL)
Vincent is also the one that knows that leaf code best, he did the
backport, you're not going to get better than that.
next prev parent reply other threads:[~2020-12-02 9:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:56 FAILED: patch "[PATCH] sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list" failed to apply to 5.4-stable tree Guilherme G. Piccoli
2020-11-19 14:57 ` Guilherme Piccoli
[not found] ` <BN8PR12MB297872B12C4DBE0793605F9B9AE00@BN8PR12MB2978.namprd12.prod.outlook.com>
2020-11-19 17:45 ` Guilherme Piccoli
2020-11-19 18:57 ` Sasha Levin
2020-11-20 5:04 ` Nivedita Singhvi
2020-12-01 15:03 ` Guilherme G. Piccoli
2020-12-02 7:51 ` Greg KH
2020-12-02 8:21 ` Vincent Guittot
2020-12-02 9:44 ` Peter Zijlstra [this message]
2020-12-02 13:52 ` Sasha Levin
2020-12-06 9:57 ` Greg KH
2020-12-11 4:00 ` Nivedita Singhvi
-- strict thread matches above, loose matches on Subject: below --
2020-05-25 14:42 gregkh
2020-05-25 17:27 ` Vincent Guittot
2020-05-26 0:22 ` Sasha Levin
2020-12-06 9:57 ` Greg KH
2020-12-06 11:25 ` Vincent Guittot
2020-12-06 11:40 ` Greg KH
2020-12-06 11:54 ` Vincent Guittot
2020-12-06 12:07 ` Greg KH
2020-12-06 12:10 ` Vincent Guittot
2020-12-06 15:18 ` Sasha Levin
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=20201202094428.GC3040@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=gavin.guo@canonical.com \
--cc=gpiccoli@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=halves@canonical.com \
--cc=jay.vosburgh@canonical.com \
--cc=mingo@redhat.com \
--cc=nivedita.singhvi@canonical.com \
--cc=pauld@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=zohooouoto@zoho.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).