linux-kernel - Re: [PATCH linux-next] ASoC: SOF: intel: remove duplicate include

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: <162988521424.7213.4488311947948918308.b4-ty@kernel.org>
Date:   Wed, 25 Aug 2021 11:22:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     CGEL <cgel.zte@...il.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc:     Mark Brown <broonie@...nel.org>, Bard Liao <bard.liao@...el.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Takashi Iwai <tiwai@...e.com>,
        sound-open-firmware@...a-project.org,
        Jaroslav Kysela <perex@...ex.cz>,
        Changcheng Deng <deng.changcheng@....com.cn>,
        Daniel Baluta <daniel.baluta@....com>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
        Zeal Robot <zealci@....com.cn>,
        Guennadi Liakhovetski <guennadi.liakhovetski@...ux.intel.com>
Subject: Re: [PATCH linux-next] ASoC: SOF: intel: remove duplicate include

On Mon, 23 Aug 2021 20:00:15 -0700, CGEL wrote:
> From: Changcheng Deng <deng.changcheng@....com.cn>
> 
> Clean up the following includecheck warning:
> 
> ./sound/soc/sof/intel/pci-tng.c: shim.h is included more than once.
> 
> No functional change.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: intel: remove duplicate include
      commit: 0be10d7122ceb8f322086283420a59ee89c1947f

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