linux-kernel - Re: [PATCH] ASoC: SOF: imx8m: Fix DSP control regmap retrieval

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: <172113637026.45643.5951000884693436336.b4-ty@kernel.org>
Date: Tue, 16 Jul 2024 14:26:10 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, 
 "Daniel Baluta (OSS)" <daniel.baluta@....nxp.com>
Cc: lgirdwood@...il.com, peter.ujfalusi@...ux.intel.com, 
 yung-chuan.liao@...ux.intel.com, ranjani.sridharan@...ux.intel.com, 
 daniel.baluta@...il.com, kernel@...gutronix.de, iuliana.prodan@....com, 
 shengjiu.wang@....com, laurentiu.mihalcea@....com, imx@...ts.linux.dev, 
 linux-kernel@...r.kernel.org, Daniel Baluta <daniel.baluta@....com>
Subject: Re: [PATCH] ASoC: SOF: imx8m: Fix DSP control regmap retrieval

On Mon, 15 Jul 2024 18:16:53 +0300, Daniel Baluta (OSS) wrote:
> According to Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
> fsl,dsp-ctrl is a phandle to syscon block so we need to use correct
> function to retrieve it.
> 
> Currently there is no SOF DSP DTS merged into mainline so there is no
> need to support the old way of retrieving the dsp control node.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: imx8m: Fix DSP control regmap retrieval
      commit: 2634f745eac25a33f032df32cf98fca8538a534a

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