linux-kernel - Re: (subset) [PATCH v2 0/3] ASoC: dt-bindings: Add bindings for WCD9335 DAIs

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: <165658956629.346792.3984245362995741043.b4-ty@kernel.org>
Date:   Thu, 30 Jun 2022 12:46:06 +0100
From:   Mark Brown <broonie@...nel.org>
To:     yassine.oudjana@...il.com, bjorn.andersson@...aro.org,
        srinivas.kandagatla@...aro.org, lgirdwood@...il.com,
        krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
        perex@...ex.cz, bgoswami@...cinc.com, tiwai@...e.com,
        agross@...nel.org
Cc:     linux-arm-msm@...r.kernel.org, y.oudjana@...tonmail.com,
        phone-devel@...r.kernel.org, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: (subset) [PATCH v2 0/3] ASoC: dt-bindings: Add bindings for WCD9335 DAIs

On Wed, 22 Jun 2022 20:13:19 +0400, Yassine Oudjana wrote:
> Add DT bindings for WCD9335 DAIs and use them in the driver as well
> as all device trees currently using WCD9335.
> 
> Changes since v1:
>  - Make header guard match path
>  - Maintain the alphabetical order in msm8996-xiaomi-gemini includes
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: dt-bindings: Add bindings for WCD9335 DAIs
      commit: 53447365ccb442bbd3dfffc2d7fd96203770dfb6
[2/3] ASoC: wcd9335: Use DT bindings instead of local DAI definitions
      commit: 66348f178d5a842c8afe52c3b743fb4af24cdb2a

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