* ARM: dts: qcom: apq8064: correct clock names
@ 2021-08-09 19:38 David Heidelberg
2021-08-10 5:59 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: David Heidelberg @ 2021-08-09 19:38 UTC (permalink / raw)
To: stable
commit 0dc6c59892ead17a9febd11202c9f6794aac1895
Hello!
since the commit b0530eb1191307e9038d75e5c83973a396137681 (just before
5.10 LTS) - this fix is needed for running Linux kernel on the APQ8064
and since is this fix apq8064 specific, shouldn't in worst case
scenario break anything else and it's tested on the Nexus 7 2013
tablet, I'm proposing backporting it to 5.10 kernel.
Without this fix 5.10 failing on dmesg panic (as described in commit):
msm_dsi 4700000.mdss_dsi: dev_pm_opp_set_clkname: Couldn't find clock:
-2
For earlier kernels before 5.10 this patch shouldn't matter and
delivers no functionality change.
Thank you
Best regards
David Heidelberg
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ARM: dts: qcom: apq8064: correct clock names
2021-08-09 19:38 ARM: dts: qcom: apq8064: correct clock names David Heidelberg
@ 2021-08-10 5:59 ` Greg KH
2021-08-10 8:16 ` David Heidelberg
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2021-08-10 5:59 UTC (permalink / raw)
To: David Heidelberg; +Cc: stable
On Mon, Aug 09, 2021 at 09:38:45PM +0200, David Heidelberg wrote:
> commit 0dc6c59892ead17a9febd11202c9f6794aac1895
What commit id is that? I do not see that in Linus's tree :(
> Hello!
>
> since the commit b0530eb1191307e9038d75e5c83973a396137681 (just before 5.10
> LTS) - this fix is needed for running Linux kernel on the APQ8064 and since
> is this fix apq8064 specific, shouldn't in worst case scenario break
> anything else and it's tested on the Nexus 7 2013 tablet, I'm proposing
> backporting it to 5.10 kernel.
What commit exactly?
confused,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ARM: dts: qcom: apq8064: correct clock names
2021-08-10 5:59 ` Greg KH
@ 2021-08-10 8:16 ` David Heidelberg
0 siblings, 0 replies; 3+ messages in thread
From: David Heidelberg @ 2021-08-10 8:16 UTC (permalink / raw)
To: Greg KH; +Cc: stable
I haven't realized it's still merged only in linux-next, so I mailed
person who commited my PATCH to add Cc for stable before it goes to the
Linus tree, sorry for confusion :)
Best regards
David Heidelberg
On Tue, Aug 10 2021 at 07:59:25 +0200, Greg KH
<gregkh@linuxfoundation.org> wrote:
> On Mon, Aug 09, 2021 at 09:38:45PM +0200, David Heidelberg wrote:
>> commit 0dc6c59892ead17a9febd11202c9f6794aac1895
>
> What commit id is that? I do not see that in Linus's tree :(
>
>> Hello!
>>
>> since the commit b0530eb1191307e9038d75e5c83973a396137681 (just
>> before 5.10
>> LTS) - this fix is needed for running Linux kernel on the APQ8064
>> and since
>> is this fix apq8064 specific, shouldn't in worst case scenario break
>> anything else and it's tested on the Nexus 7 2013 tablet, I'm
>> proposing
>> backporting it to 5.10 kernel.
>
> What commit exactly?
>
> confused,
>
> greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-08-10 8:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-08-09 19:38 ARM: dts: qcom: apq8064: correct clock names David Heidelberg
2021-08-10 5:59 ` Greg KH
2021-08-10 8:16 ` David Heidelberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox