linux-kernel - Re: [PATCH] soc: qcom: pmic_glink: disable UCSI on sc8280xp

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]

Date: Mon, 17 Jun 2024 11:08:23 +0200
From: Johan Hovold <johan@...nel.org>
To: Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] soc: qcom: pmic_glink: disable UCSI on sc8280xp

On Mon, Jun 17, 2024 at 10:49:40AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 17.06.24 09:56, Johan Hovold wrote:
> > On Sat, Jun 08, 2024 at 01:45:29PM +0200, Johan Hovold wrote:

> > I noticed

> > that this one did not make into the regression tracker.
> 
> FWIW, it did:
> 
> https://linux-regtracking.leemhuis.info/regzbot/regression/lore/20240608114529.23060-1-johan+linaro@kernel.org/
> 
> > This
> > may be related to the fact that this is the second time I'm disabling
> > UCSI on sc8280xp and apparently I used the same patch Subject last time
> > so they end up in the same thread on lore:
> > 	https://lore.kernel.org/lkml/20240608114529.23060-1-johan+linaro@kernel.org/
> 
> Kinda. The thread is not the problem. I told regzbot about the subject
> for the fix a few days ago and it then dutifully looked up if a commit
> with that subject ended up in next or mainline already. Which normally
> is the right thing to do -- but in this case it went sideways for
> obvious reasons. :-/ Not sure yet how to handle that better; maybe that
> falls into the ugly category called "there are bigger fish to fry,
> ignore this corner case for now".

Fair enough. At least it's a known issue then.

Johan