[PATCH] ASoC: wm_adsp: remove a repeated including

[PATCH] ASoC: wm_adsp: remove a repeated including

[Guo Zhengkui]

Remove a repeated "#include <linux/firmware.h>" in line 32.

Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>
---
 sound/soc/codecs/wm_adsp.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sound/soc/codecs/wm_adsp.c b/sound/soc/codecs/wm_adsp.c
index 6c5d55b3b311..b9fb4f547d5e 100644
--- a/sound/soc/codecs/wm_adsp.c
+++ b/sound/soc/codecs/wm_adsp.c
@@ -29,7 +29,6 @@
 #include <sound/jack.h>
 #include <sound/initval.h>
 #include <sound/tlv.h>
-#include <linux/firmware.h>
 
 #include "wm_adsp.h"
 
-- 
2.20.1

RE: [PATCH] ASoC: wm_adsp: remove a repeated including

[Simon Trimmer]

On Wednesday, September 29, 2021 1:32 PM, Guo Zhengkui wrote:
> Remove a repeated "#include <linux/firmware.h>" in line 32.
> 
> Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>
> ---

Acked-by: Simon Trimmer <simont@opensource.cirrus.com>

Thanks,
Simon

Re: [PATCH] ASoC: wm_adsp: remove a repeated including

[Mark Brown]

On Wed, 29 Sep 2021 20:32:15 +0800, Guo Zhengkui wrote:
> Remove a repeated "#include <linux/firmware.h>" in line 32.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: wm_adsp: remove a repeated including
      commit: 626605a3dfb5c538256e737a7a7ae3e18f3368ec

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