All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] cpufreq/arm updates for 5.13
Date: Mon, 12 Apr 2021 14:48:55 +0200	[thread overview]
Message-ID: <CAJZ5v0ggj4LP4D2FXs=CyFAcnfFFyqdjtuQjJ3xDJGNhjp8eSg@mail.gmail.com> (raw)
In-Reply-To: <20210412054832.6wxa7b5weu6upmxb@vireshk-i7>

On Mon, Apr 12, 2021 at 7:48 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> Hi Rafael,
>
> This pull request contains:
>
> - Fix typos in s5pv210 cpufreq driver (Bhaskar Chowdhury).
>
> - Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz
>   (Pali Rohár and Marek Behún).
>
> - cpufreq-dt: Return -EPROBE_DEFER on failure to add table (Quanyang Wang).
>
> - Minor cleanup in cppc driver (Tom Saeger).
>
> - Add frequency invariance support for CPPC driver and generalize freq
>   invariance support arch-topology driver (Viresh Kumar).
>
> Thanks.
>
> --
> Viresh
>
> -------------------------8<-------------------------
>
> The following changes since commit fbb31cb805fd3574d3be7defc06a7fd2fd9af7d2:
>
>   cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev (2021-03-08 16:20:07 +0530)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/arm/linux-next
>
> for you to fetch changes up to dbbd49bade0548db87ceb1943951dea456af2e22:
>
>   cpufreq: armada-37xx: Fix module unloading (2021-04-09 15:17:33 +0530)

Pulled, thanks!

      reply	other threads:[~2021-04-12 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  5:48 [GIT PULL] cpufreq/arm updates for 5.13 Viresh Kumar
2021-04-12 12:48 ` 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='CAJZ5v0ggj4LP4D2FXs=CyFAcnfFFyqdjtuQjJ3xDJGNhjp8eSg@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=viresh.kumar@linaro.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 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.