linux-kernel - Re: [PATCH 2/2] arm64: dts: qcom: msm8996: add interconnect paths to USB2 controller

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] [day] [month] [year] [list]

Message-ID: <siil3r5vj4afnwvo4pp53kj2gjontwb6q7jvl3vixceydhxwlf@vx7mqqd6hyji>
Date: Thu, 30 Oct 2025 13:52:33 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>, 
	Georgi Djakov <djakov@...nel.org>, Yassine Oudjana <y.oudjana@...tonmail.com>, 
	Dmitry Baryshkov <lumag@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: msm8996: add interconnect paths to
 USB2 controller

On Thu, Oct 30, 2025 at 08:24:29PM +0200, Dmitry Baryshkov wrote:
> On Mon, Oct 06, 2025 at 11:30:52AM +0200, Konrad Dybcio wrote:
> > On 10/2/25 10:53 AM, Dmitry Baryshkov wrote:
> > > Add the missing interconnects to the USB2 host. The Fixes tag points to
> > > the commit which broke probing of the USB host on that platform.
> > > 
> > > Fixes: 130733a10079 ("interconnect: qcom: msm8996: Promote to core_initcall")
> > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
> > > 
> > > ---
> > > Note: without the previous patch applying this one can result in the
> > > kernel stuck at booting because of the EPROBE_DEFER loop. I suggest
> > > applying them through the same tree in order to make sure that the tree
> > > is not broken (or using an immutable tag for the icc commit).
> > > ---
> > 
> > There seems to be syntax for this, at least for stable patches
> > (which we should probably either use or add +noautosel):
> > 
> > * Specify any additional patch prerequisites for cherry picking::
> > 
> >     xCxc: <stable@...r.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
> >     xCxc: <stable@...r.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
> >     xCxc: <stable@...r.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
> >     xCxc: <stable@...r.kernel.org> # 3.3.x
> >     xSxixgxxnxexd-oxfxf-xbxy: Ingo Molnar <mingo@...e.hu>
> > 
> > (deliberatelly added a bunch of 'x'-es to not interrupt the maintainers'
> > b4 workflow)
> 
> Bjorn, Georgi, Konrad, how should we proceed with this series?
> 

I agree with you on the Cc part, that doesn't affect how these patches
shows up in torvalds/master during the merge window. So merging them in
the same branch would be the way.

@Georgi, I'm fine with doing this in either tree, if you prefer to pick
the two patches:

Acked-by: Bjorn Andersson <andersson@...nel.org>

Regards,
Bjorn

> -- 
> With best wishes
> Dmitry