linux-kernel - Re: [PATCH] Revert "ASoC: dt-bindings: mediatek: mt8192: Add i2s-share properties"

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: <165212626102.1478109.3697258153804528211.b4-ty@kernel.org>
Date:   Mon, 09 May 2022 20:57:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     nfraprado@...labora.com
Cc:     angelogioacchino.delregno@...labora.com,
        linux-arm-kernel@...ts.infradead.org, matthias.bgg@...il.com,
        robh+dt@...nel.org, jiaxin.yu@...iatek.com,
        alsa-devel@...a-project.org, shane.chien@...iatek.com,
        lgirdwood@...il.com, linux-mediatek@...ts.infradead.org,
        kernel@...labora.com, krzk+dt@...nel.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] Revert "ASoC: dt-bindings: mediatek: mt8192: Add i2s-share properties"

On Mon, 9 May 2022 14:56:25 -0400, Nícolas F. R. A. Prado wrote:
> This reverts commit e056cf4341ae3f856f1e38da02b27cb04de4c69b. The commit
> was merged while the property name and definition were still being
> discussed. Revert the commit for now and a follow up commit will re-add
> the property after it is further discussed and reviewed.
> 
> 

Applied to

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

Thanks!

[1/1] Revert "ASoC: dt-bindings: mediatek: mt8192: Add i2s-share properties"
      commit: d94d1486952b860dcedd04d0ff8ade2176418905

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