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: <165099287726.2323572.10174502705514813349.b4-ty@kernel.org>
Date:   Tue, 26 Apr 2022 18:07:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     stephan@...hold.net, devicetree@...r.kernel.org, perex@...ex.cz,
        tiwai@...e.com, lgirdwood@...il.com, ckeepax@...nsource.cirrus.com,
        lukas.bulwahn@...il.com, pbrobinson@...il.com, krzk+dt@...nel.org,
        cy_huang@...htek.com, ryan.lee.analog@...il.com,
        pierre-louis.bossart@...ux.intel.com,
        srinivas.kandagatla@...aro.org, hdegoede@...hat.com,
        drhodes@...nsource.cirrus.com, tanureal@...nsource.cirrus.com,
        linux-kernel@...r.kernel.org, ryans.lee@...log.com,
        Arnd Bergmann <arnd@...db.de>, robh+dt@...nel.org,
        alsa-devel@...a-project.org
Cc:     lkp@...el.com
Subject: Re: [PATCH V3 2/2] ASoC: max98396: add amplifier driver

On Fri, 22 Apr 2022 19:15:58 -0700, Ryan Lee wrote:
> This series of patches adds support for Analog Devices MAX98396
> mono amplifier with IV sense. The device provides a PCM interface
> for audio data and a standard I2C interface for control data
> communication. This driver also supports MAX98397 which is
> a variant of MAX98396 with wide input supply range.
> 
> 
> [...]

Applied to

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

Thanks!

[2/2] ASoC: max98396: add amplifier driver
      commit: b58581136770569d2ee4300b10c7c0d76bb86250

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ