From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Dmitry Osipenko <digetx@gmail.com>, He Ying <heying24@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] cpuidle for v5.13-rc1
Date: Thu, 8 Apr 2021 20:07:45 +0200 [thread overview]
Message-ID: <CAJZ5v0iT28V07sg1cPTvNur4=y=H7pBw2FQZNMoMggmDVsWh2A@mail.gmail.com> (raw)
In-Reply-To: <4b8b0bc5-492c-7e95-9b08-ab87c9ac65d5@linaro.org>
On Thu, Apr 8, 2021 at 8:02 PM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> On 08/04/2021 19:24, Rafael J. Wysocki wrote:
> > On Thu, Apr 8, 2021 at 5:10 PM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
> >>
> >>
> >> Hi Rafael,
> >>
> >> please consider pulling the following change for cpuidle on ARM for
> >> v5.13-rc1
> >>
> >> Thanks
> >>
> >> -- Daniel
> >>
> >>
> >> The following changes since commit dde8740bd9b505c58ec8b2277d5d55c6951b7e42:
> >>
> >> Merge branch 'acpi-processor-fixes' into linux-next (2021-04-07
> >> 19:02:56 +0200)
> >
> > Can you please rebase this on 5.12-rc6? My linux-next branch is
> > re-merged on a regular basis.
> >
> > Generally speaking, if you want me to pull from a branch, please make
> > sure that this branch is based on a commit present in the Linus' tree,
> > preferably one of the commits tagged as -rc or a specific merge.
> >
>
> Sure, here is the pull request based on v5.12-rc6 with the signed tag
> cpuidle-v5.13-rc1
Pulled, thanks!
> The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:
>
> Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)
>
> are available in the Git repository at:
>
> https://git.linaro.org/people/daniel.lezcano/linux tags/cpuidle-v5.13-rc1
>
> for you to fetch changes up to 498ba2a8a2756694b6f3888857426dbc8a5e6b6c:
>
> cpuidle: Fix ARM_QCOM_SPM_CPUIDLE configuration (2021-04-08 19:54:14
> +0200)
>
> ----------------------------------------------------------------
> - Fix the C7 state on the tegra114 by setting the L2-no-flush flag
> unconditionally (Dmitry Osipenko)
>
> - Remove the do_idle firmware call as it is not supported by the ATF
> on tegra SoC (Dmitry Osipenko)
>
> - Add a missing dependency on CONFIG_MMU to prevent linkage error (He
> Ying)
>
> ----------------------------------------------------------------
> Dmitry Osipenko (2):
> cpuidle: tegra: Fix C7 idling state on Tegra114
> cpuidle: tegra: Remove do_idle firmware call
>
> He Ying (1):
> cpuidle: Fix ARM_QCOM_SPM_CPUIDLE configuration
>
> drivers/cpuidle/Kconfig.arm | 2 +-
> drivers/cpuidle/cpuidle-tegra.c | 19 ++++---------------
> 2 files changed, 5 insertions(+), 16 deletions(-)
>
> --
> <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
>
> Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
> <http://twitter.com/#!/linaroorg> Twitter |
> <http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2021-04-08 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 15:10 [GIT PULL] cpuidle for v5.13-rc1 Daniel Lezcano
2021-04-08 17:24 ` Rafael J. Wysocki
2021-04-08 18:02 ` Daniel Lezcano
2021-04-08 18:07 ` Rafael J. Wysocki [this message]
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='CAJZ5v0iT28V07sg1cPTvNur4=y=H7pBw2FQZNMoMggmDVsWh2A@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=digetx@gmail.com \
--cc=heying24@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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).