linux-kernel - Re: [RESEND v2 0/3] Add support for XCVR on i.MX93 platform

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <167328294977.323147.11170247431537947432.b4-ty@kernel.org>
Date:   Mon, 09 Jan 2023 16:49:09 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, shengjiu.wang@...il.com,
        Xiubo.Lee@...il.com, festevam@...il.com, nicoleotsuka@...il.com,
        perex@...ex.cz, tiwai@...e.com, devicetree@...r.kernel.org,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        Chancel Liu <chancel.liu@....com>
Subject: Re: [RESEND v2 0/3] Add support for XCVR on i.MX93 platform

On Wed, 04 Jan 2023 10:39:50 +0800, Chancel Liu wrote:
> This patchset supports XCVR on i.MX93 platform.
> 
> changes in v2:
> - remove unnecessary code which causes kernel test robot reporting error
> 
> Chancel Liu (3):
>   ASoC: dt-bindings: fsl,xcvr: Add compatible string for i.MX93 platform
>   ASoC: fsl_xcvr: Add support for i.MX93 platform
>   ASoC: fsl_xcvr: Add constraints of period size while using eDMA
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: dt-bindings: fsl,xcvr: Add compatible string for i.MX93 platform
      commit: 0a22003c637b71a1dbd8bb521c09736b52349256
[2/3] ASoC: fsl_xcvr: Add support for i.MX93 platform
      commit: e240b9329a300af7b7c1eba2ce0abbf19e6c540b
[3/3] ASoC: fsl_xcvr: Add constraints of period size while using eDMA
      commit: 1760df5b7ee6a0bfc8ad47f4db490c36c5546be8

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