linux-kernel - Re: [PATCH v5 1/2] ASoC: amd: Add support for RT5682 codec in machine 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <161641797251.25992.139451453109004005.b4-ty@kernel.org>
Date:   Mon, 22 Mar 2021 13:00:31 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Vijendar Mukunda <Vijendar.Mukunda@....com>,
        alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>,
        Chuhong Yuan <hslester96@...il.com>,
        Arnd Bergmann <arnd@...db.de>,
        Liam Girdwood <lgirdwood@...il.com>,
        Sunil-kumar.Dommati@....com,
        open list <linux-kernel@...r.kernel.org>, shumingf@...ltek.com,
        Takashi Iwai <tiwai@...e.com>, Basavaraj.Hiregoudar@....com,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Ravulapati Vishnu vardhan rao 
        <Vishnuvardhanrao.Ravulapati@....com>, derek.fang@...ltek.com,
        Alexander.Deucher@....com, flove@...ltek.com,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Subject: Re: [PATCH v5 1/2] ASoC: amd: Add support for RT5682 codec in machine driver

On Fri, 19 Mar 2021 07:10:42 +0530, Vijendar Mukunda wrote:
> Add support for RT5682 codec in machine driver.

Applied to

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

Thanks!

[1/2] ASoC: amd: Add support for RT5682 codec in machine driver
      commit: 7e71b48f9e27e437ca523432ea285c2585a539dc

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