linux-kernel - Re: [PATCH] regulator: qcom-labibb: OCP interrupts are not a failure while disabled

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: <164036266175.3720266.13529108336109588098.b4-ty@kernel.org>
Date:   Fri, 24 Dec 2021 16:17:41 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Marijn Suijten <marijn.suijten@...ainline.org>,
        phone-devel@...r.kernel.org
Cc:     Pavel Dubrova <pashadubrova@...il.com>,
        linux-kernel@...r.kernel.org,
        Martin Botka <martin.botka@...ainline.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...ainline.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        Jami Kettunen <jami.kettunen@...ainline.org>,
        Andy Gross <agross@...nel.org>,
        ~postmarketos/upstreaming@...ts.sr.ht,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] regulator: qcom-labibb: OCP interrupts are not a failure while disabled

On Fri, 24 Dec 2021 12:34:50 +0100, Marijn Suijten wrote:
> Receiving the Over-Current Protection interrupt while the regulator is
> disabled does not count as unhandled/failure (IRQ_NONE, or 0 as it were)
> but a "fake event", usually due to inrush as the is regulator about to
> be enabled.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: qcom-labibb: OCP interrupts are not a failure while disabled
      commit: d27bb69dc83f00f86a830298c967052cded6e784

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark