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 fixes for 5.12
Date: Thu, 18 Feb 2021 18:42:30 +0100	[thread overview]
Message-ID: <CAJZ5v0h9rs9LQvSN2d881C7oR7VL_PLfDHX5zK8MLeKTyFxcKg@mail.gmail.com> (raw)
In-Reply-To: <20210218091849.6lem2iaags3dsrz3@vireshk-i7>

On Thu, Feb 18, 2021 at 10:18 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> Hi Rafael,
>
> This pull request contains a single patch to fix issue with cpu hotplug and
> policy recreation for qcom-cpufreq-hw driver..
>
> Thanks.
>
> --
> Viresh
>
> -------------------------8<-------------------------
>
> The following changes since commit 7114ebffd330bfc5a95b9832a70b6bd857d26fd8:
>
>   cpufreq: remove tango driver (2021-01-21 09:34:46 +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 67fc209b527d023db4d087c68e44e9790aa089ef:
>
>   cpufreq: qcom-hw: drop devm_xxx() calls from init/exit hooks (2021-02-18 14:35:18 +0530)

Pulled, thanks!

Please note that this will be pushed after the previous PM pull
request has been merged, though.

  reply	other threads:[~2021-02-18 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18  9:18 [GIT PULL] cpufreq/arm fixes for 5.12 Viresh Kumar
2021-02-18 17:42 ` Rafael J. Wysocki [this message]
2021-03-08 10:56 Viresh Kumar
2021-03-08 16:02 ` Rafael J. Wysocki

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=CAJZ5v0h9rs9LQvSN2d881C7oR7VL_PLfDHX5zK8MLeKTyFxcKg@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.