linux-kernel - Re: [PATCH V4 1/2] ASoC: max98363: add soundwire amplifier driver

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: <168027496197.3365708.8821025322937971454.b4-ty@kernel.org>
Date:   Fri, 31 Mar 2023 16:02:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        krzysztof.kozlowski@...aro.org, rf@...nsource.cirrus.com,
        ckeepax@...nsource.cirrus.com,
        pierre-louis.bossart@...ux.intel.com, herve.codina@...tlin.com,
        wangweidong.a@...nic.com, james.schulman@...rus.com,
        ajye_huang@...pal.corp-partner.google.com, shumingf@...ltek.com,
        povik+lin@...ebit.org, flatmax@...tmax.com,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        robh+dt@...nel.org, devicetree@...r.kernel.org,
        ryans.lee@...log.com,
        “Ryan <ryan.lee.analog@...il.com>
Subject: Re: [PATCH V4 1/2] ASoC: max98363: add soundwire amplifier driver

On Thu, 30 Mar 2023 16:43:18 -0700, “Ryan wrote:
> Added Analog Devices MAX98363 SoundWire Amplifier Driver.
> The MAX98363 is a SoundWire peripheral device that supports
> MIPI SoundWire v1.2-compatible digital interface for audio and
> control data.
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/2] ASoC: max98363: add soundwire amplifier driver
      commit: 18c0af945fa35766730d3f729adcf417a3d1ad5d
[2/2] ASoC: dt-bindings: max98363: add soundwire amplifier
      commit: 276d8c08e82b9f6062f6febc7bc63913829bde27

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