linux-kernel - Re: [PATCH] spi: qup: Request DMA before enabling clocks

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: <168545610674.311273.7922525088793753962.b4-ty@kernel.org>
Date:   Tue, 30 May 2023 15:15:06 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Stephan Gerhold <stephan@...hold.net>
Cc:     Bjorn Andersson <andersson@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Stanimir Varbanov <stanimir.varbanov@...aro.org>,
        linux-arm-msm@...r.kernel.org, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: qup: Request DMA before enabling clocks

On Thu, 18 May 2023 15:04:25 +0200, Stephan Gerhold wrote:
> It is usually better to request all necessary resources (clocks,
> regulators, ...) before starting to make use of them. That way they do
> not change state in case one of the resources is not available yet and
> probe deferral (-EPROBE_DEFER) is necessary. This is particularly
> important for DMA channels and IOMMUs which are not enforced by
> fw_devlink yet (unless you use fw_devlink.strict=1).
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: qup: Request DMA before enabling clocks
      commit: 0c331fd1dccfba657129380ee084b95c1cedfbef

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