From: Sasha Levin <sashal@kernel.org>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: peterz@infradead.org,
Vincent Guittot <vincent.guittot@linaro.org>,
bsegall@google.com, gregkh@linuxfoundation.org, pauld@redhat.com,
zohooouoto@zoho.com.cn, stable@vger.kernel.org,
Gavin Guo <gavin.guo@canonical.com>,
nivedita.singhvi@canonical.com, halves@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: Thu, 19 Nov 2020 13:57:09 -0500 [thread overview]
Message-ID: <20201119185709.GD643756@sasha-vm> (raw)
In-Reply-To: <d3188913-ddb8-7198-8483-47d3031b01fe@canonical.com>
On Thu, Nov 19, 2020 at 11:56:01AM -0300, Guilherme G. Piccoli wrote:
>Hi Sasha / Peter, is there anything blocking this backport from Vincent
>to get merged in 5.4.y?
An ack from Peter...
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-11-19 18:57 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 [this message]
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
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=20201119185709.GD643756@sasha-vm \
--to=sashal@kernel.org \
--cc=bsegall@google.com \
--cc=gavin.guo@canonical.com \
--cc=gpiccoli@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=halves@canonical.com \
--cc=nivedita.singhvi@canonical.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.