Skip to contentSkip to conversation

ASoC: SOF: Intel: Remove duplicated include in lnl.c

PATCH In review Yang Li 3 participants 3 messages Aug 10, 2023

Subsystems (3)
lore
Share & tools
lore

Yang Li

author
#0 lore raw

PATCH 1/1 ASoC: SOF: Intel: Remove duplicated include in lnl.c

./sound/soc/sof/intel/lnl.c: hda.h is included more than once.

---
 sound/soc/sof/intel/lnl.c | 1 -
 1 file changed, 1 deletion(-)
sound/soc/sof/intel/lnl.c +0 -1
index 3d919b0b6891..db94b45e53af 100644
@@ -16,7 +16,6 @@
 #include "hda-ipc.h"
 #include "../sof-audio.h"
 #include "mtl.h"
-#include "hda.h"
 #include <sound/hda-mlink.h>
 
 /* LunarLake ops */
Signature · 1 line
2.20.1.7.g153144c
Acked-by on v1 1/1
#1 lore raw
Quoted 3 lines · Yang Li

./sound/soc/sof/intel/lnl.c: hda.h is included more than once.

yes, thanks for the patch

Quoted 16 lines
---
 sound/soc/sof/intel/lnl.c | 1 -
 1 file changed, 1 deletion(-)
sound/soc/sof/intel/lnl.c +0 -1
index 3d919b0b6891..db94b45e53af 100644
@@ -16,7 +16,6 @@
 #include "hda-ipc.h"
 #include "../sof-audio.h"
 #include "mtl.h"
-#include "hda.h"
 #include <sound/hda-mlink.h>
 
 /* LunarLake ops */
maintainer
#2 lore raw
In reply to Yang Li
Quoted 3 lines · Yang Li

./sound/soc/sof/intel/lnl.c: hda.h is included more than once.

Applied to

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

Thanks!

[1/1] ASoC: SOF: Intel: Remove duplicated include in lnl.c

      commit: 061599c8285848fe4ec64becb278dcdd60dd3369

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