linux-kernel - Re: [PATCH 5.15 087/317] arm64: dts: qcom: msm8998: drop USB PHY clock index

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: Windows password security audit tool. GUI, reports in PDF.

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

Date: Mon, 25 Mar 2024 08:42:55 +0100
From: Johan Hovold <johan@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Johan Hovold <johan+linaro@...nel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
	Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: [PATCH 5.15 087/317] arm64: dts: qcom: msm8998: drop USB PHY
 clock index

On Sun, Mar 24, 2024 at 07:31:07PM -0400, Sasha Levin wrote:
> From: Johan Hovold <johan+linaro@...nel.org>
> 
> [ Upstream commit ed9cbbcb8c6a1925db7995214602c6a8983ff870 ]
> 
> The QMP USB PHY provides a single clock so drop the redundant clock
> index.
> 
> Signed-off-by: Johan Hovold <johan+linaro@...nel.org>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@...aro.org>
> Link: https://lore.kernel.org/r/20220705114032.22787-7-johan+linaro@kernel.org
> Stable-dep-of: fc835b2311d4 ("arm64: dts: qcom: msm8998: declare VLS CLAMP register for USB3 PHY")

As I also already pointed out once, this patch does not make sense to
backport and neither does the Stable-dep-of which depends on a new
driver in 6.9.

Please drop from all stable queues, including the other deps that will
break the driver such as:

	b7efebfeb2e8 ("arm64: dts: qcom: msm8998: switch USB QMP PHY to new style of bindings")

Sasha, you can't around picking intrusive patches like this on your own.

The Stable-dep-of did not have a stable tag and should never have been a
candidate for backporting in the first place.

Having to point this out to you twice in two days is quite frustrating
and I'm worried about what breaks next time when I happen to look away.

Johan