All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Ionela Voinescu <ionela.voinescu@arm.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Will Deacon <will@kernel.org>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Linux PM <linux-pm@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/5] cpufreq: improve frequency invariance support
Date: Fri, 18 Sep 2020 19:12:24 +0200	[thread overview]
Message-ID: <CAJZ5v0iw4pRpGxXCR6pB9o+ynsNLAHPug-XyPWZktJ7i6TPtHQ@mail.gmail.com> (raw)
In-Reply-To: <20200904043847.g4ss3o4uofwujnyk@vireshk-i7>

On Fri, Sep 4, 2020 at 6:39 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 03-09-20, 14:32, Ionela Voinescu wrote:
> > Hi Rafael, Viresh,
> >
> > Would it be okay for you to apply this series, as the majority of
> > changes are in cpufreq? For arch_topology and arm64 changes, they have
> > been reviewed and acked-by Catalin and Sudeep.
> >
> > Also, please let me know if I should send v6 with Sudeep's Reviewed-by/s
> > applied.
>
> No need to resend. Rafael will apply these with the tags.

Right. :-)

So now applied as 5.10 material, sorry for the delay.

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Ionela Voinescu <ionela.voinescu@arm.com>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Will Deacon <will@kernel.org>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/5] cpufreq: improve frequency invariance support
Date: Fri, 18 Sep 2020 19:12:24 +0200	[thread overview]
Message-ID: <CAJZ5v0iw4pRpGxXCR6pB9o+ynsNLAHPug-XyPWZktJ7i6TPtHQ@mail.gmail.com> (raw)
In-Reply-To: <20200904043847.g4ss3o4uofwujnyk@vireshk-i7>

On Fri, Sep 4, 2020 at 6:39 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 03-09-20, 14:32, Ionela Voinescu wrote:
> > Hi Rafael, Viresh,
> >
> > Would it be okay for you to apply this series, as the majority of
> > changes are in cpufreq? For arch_topology and arm64 changes, they have
> > been reviewed and acked-by Catalin and Sudeep.
> >
> > Also, please let me know if I should send v6 with Sudeep's Reviewed-by/s
> > applied.
>
> No need to resend. Rafael will apply these with the tags.

Right. :-)

So now applied as 5.10 material, sorry for the delay.

Thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-09-18 17:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 20:55 [PATCH v5 0/5] cpufreq: improve frequency invariance support Ionela Voinescu
2020-09-01 20:55 ` Ionela Voinescu
2020-09-01 20:55 ` [PATCH v5 1/5] arch_topology: validate input frequencies to arch_set_freq_scale() Ionela Voinescu
2020-09-01 20:55   ` Ionela Voinescu
2020-09-02 13:32   ` Sudeep Holla
2020-09-02 13:32     ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 2/5] cpufreq: move invariance setter calls in cpufreq core Ionela Voinescu
2020-09-01 20:55   ` Ionela Voinescu
2020-09-02 13:30   ` Sudeep Holla
2020-09-02 13:30     ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 3/5] cpufreq: report whether cpufreq supports Frequency Invariance (FI) Ionela Voinescu
2020-09-01 20:55   ` Ionela Voinescu
2020-09-02 13:28   ` Sudeep Holla
2020-09-02 13:28     ` Sudeep Holla
2020-09-03 13:45     ` Ionela Voinescu
2020-09-03 13:45       ` Ionela Voinescu
2020-09-03 14:19       ` Sudeep Holla
2020-09-03 14:19         ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 4/5] arch_topology, cpufreq: constify arch_* cpumasks Ionela Voinescu
2020-09-01 20:55   ` Ionela Voinescu
2020-09-02 13:25   ` Sudeep Holla
2020-09-02 13:25     ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 5/5] arch_topology, arm, arm64: define arch_scale_freq_invariant() Ionela Voinescu
2020-09-01 20:55   ` Ionela Voinescu
2020-09-02 13:24   ` Sudeep Holla
2020-09-02 13:24     ` Sudeep Holla
2020-09-03 13:32 ` [PATCH v5 0/5] cpufreq: improve frequency invariance support Ionela Voinescu
2020-09-03 13:32   ` Ionela Voinescu
2020-09-04  4:38   ` Viresh Kumar
2020-09-04  4:38     ` Viresh Kumar
2020-09-18 17:12     ` Rafael J. Wysocki [this message]
2020-09-18 17:12       ` 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=CAJZ5v0iw4pRpGxXCR6pB9o+ynsNLAHPug-XyPWZktJ7i6TPtHQ@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=ionela.voinescu@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.com \
    --cc=valentin.schneider@arm.com \
    --cc=viresh.kumar@linaro.org \
    --cc=will@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 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.