linux-kernel - Re: [PATCH] ASoc: adi: Kconfig: Remove depends on for ADI reference designs

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: <160565265704.23689.695597438692063700.b4-ty@kernel.org>
Date:   Tue, 17 Nov 2020 22:37:55 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        Alexandru Ardelean <alexandru.ardelean@...log.com>
Cc:     lgirdwood@...il.com, tiwai@...e.com, bogdan.togorean@...log.com
Subject: Re: [PATCH] ASoc: adi: Kconfig: Remove depends on for ADI reference designs

On Tue, 10 Nov 2020 17:22:13 +0200, Alexandru Ardelean wrote:
> Audio ADI reference designs are also used on some ZynqMP boards, and can
> also be used on Intel FPGA boards and also on some more complex FPGA
> combinations (FPGA cards connected through PCIe).
> 
> This change removes the dependency on Microblaze and Zynq architectures
> to allow the usage of this driver for the systems described above.

Applied to

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

Thanks!

[1/1] ASoc: adi: Kconfig: Remove depends on for ADI reference designs
      commit: e1ade4c55ae3559b082faf9f5207cc6caba1c546

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