linux-kernel - Re: [PATCH 1/3] dt-bindings: sound/ingenic: Add compatible strings for JZ4760(B) SoC

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: <161280948305.10741.16478273980568461792.b4-ty@kernel.org>
Date:   Mon, 08 Feb 2021 18:38:03 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>,
        Paul Cercueil <paul@...pouillou.net>,
        Jaroslav Kysela <perex@...ex.cz>,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        od@...c.me, Christophe Branchereau <cbranchereau@...il.com>,
        devicetree@...r.kernel.org, linux-mips@...r.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: sound/ingenic: Add compatible strings for JZ4760(B) SoC

On Sat, 23 Jan 2021 14:09:56 +0000, Paul Cercueil wrote:
> Add the ingenic,jz4760b-codec and ingenic,jz4760-codec compatible
> strings.
> 
> In the process, convert the previous compatible strings to use an enum
> instead.

Applied to

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

Thanks!

[1/3] dt-bindings: sound/ingenic: Add compatible strings for JZ4760(B) SoC
      commit: 45a90d4aba1781aa382d4aeedebcac7cc78e1927
[2/3] ASoC: codec/ingenic: Depend on MACH_INGENIC
      commit: bad929b81ce25bba1c3e9d91848ffdc166974256
[3/3] ASoC: codec: Add driver for JZ4760 internal codec
      commit: d9cd22e9c87cb61488d00f7279cfb2abf5238879

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