linux-kernel - Re: [PATCH] cpufreq: Register cpufreq drivers only after CPU devices are registered

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191114071845.ea62rlcbjiprx3t6@vireshk-i7>
Date:   Thu, 14 Nov 2019 12:48:45 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Amit Kucheria <amit.kucheria@...aro.org>
Cc:     Daniel Lezcano <daniel.lezcano@...aro.org>,
        Rafael Wysocki <rjw@...ysocki.net>,
        Linux PM list <linux-pm@...r.kernel.org>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpufreq: Register cpufreq drivers only after CPU devices
 are registered

On 14-11-19, 12:33, Amit Kucheria wrote:
> My series was going to get merged through the thermal tree. Currently
> it is hosted here[1] for linux-next testing. We could sign-off this
> patch to the thermal tree or bring the series into the PM tree. Up to
> Rafael and you.

Your thermal patches need to get based of this patch in that case.
Maybe just ask Rui to drop your last patch (for qcom-cpufreq-hw.c)
and merge things as planned. After rc1 is out, you can ask Rafael to
merge that one on top of rc1 ? Everything can still go in 5.5 that
way.

-- 
viresh