linux-kernel - Re: [PATCH 1/3] ASoC: samsung: s3c-i2s-v2: Allow build for unsupported hardware

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: <165641228114.254424.9239114588786840760.b4-ty@kernel.org>
Date:   Tue, 28 Jun 2022 11:31:21 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Takashi Iwai <tiwai@...e.com>, krzysztof.kozlowski@...aro.org,
        Liam Girdwood <lgirdwood@...il.com>,
        alsa-devel@...a-project.org, s.nawrocki@...sung.com,
        linux-kernel@...r.kernel.org, Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH 1/3] ASoC: samsung: s3c-i2s-v2: Allow build for unsupported hardware

On Mon, 27 Jun 2022 16:34:10 +0200, Krzysztof Kozlowski wrote:
> There is no particular need to restrict building of S3C I2S driver to
> supported platforms within the C unit, because Kconfig does it.
> Removing such restricting #ifdef from s3c-i2s-v2 allows compile testing
> it on other platforms.
> 
> 

Applied to

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

Thanks!

[1/3] ASoC: samsung: s3c-i2s-v2: Allow build for unsupported hardware
      commit: 17a1ffc7bc4d5b4657d0f3fe5c01778d8fcab9a3
[2/3] ASoC: samsung: s3c24xx-i2s: Drop unneeded gpio.h include
      commit: 3e4bac7cf06e46225322f264e7387efe6ddd457e
[3/3] ASoC: samsung: Enable compile test
      commit: f43ff8038e8289ca811b5b89e8cc15083dafe5c4

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