linux-kernel - Re: [RESEND PATCH 1/2] soc: qcom: rmtfs: allow building the module with COMPILE

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]

Message-ID: <CAMRc=MdtbgSuwjv_h7+VVr5U2frc24NYmpifPQJ0O0iQt_sWKg@mail.gmail.com>
Date: Thu, 9 Jan 2025 12:13:59 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Jens Glathe <jens.glathe@...schoolsolutions.biz>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>, 
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, 
	Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Subject: Re: [RESEND PATCH 1/2] soc: qcom: rmtfs: allow building the module
 with COMPILE_TEST=y

On Thu, Jan 9, 2025 at 10:56 AM Jens Glathe
<jens.glathe@...schoolsolutions.biz> wrote:
>
> On 02.12.24 10:49, Bartosz Golaszewski wrote:
>
> > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> >
> > Make it possible to build the module when COMPILE_TEST is enabled for
> > better build coverage.
>
> Hi Bartosz,
>
> no idea why this happens, but I just bisected my way to this patchset
> for this very odd error on the HP Omnibook X14:
>
> jglathe@...-jg:~$ sudo dmesg|grep snps
> [    1.009307] qcom-snps-eusb2-hsphy 88e1000.phy: Registered Qcom-eUSB2 phy
> [   24.035977] platform fd3000.phy: deferred probe pending:
> qcom-snps-eusb2-hsphy: failed to get repeater
> [   24.035987] platform fd9000.phy: deferred probe pending:
> qcom-snps-eusb2-hsphy: failed to get repeater
>
> This kills USB2 functionality on the type-c connectors.
>
> with best regards
>
> Jens
>

Well, that's weird. Are you 100% sure this commit is the culprit? I
have no idea how this could happen, it's just a Kconfig tweak.

Bartosz