From: Mark Brown <broonie@kernel.org>
To: Guneshwor Singh <guneshwor.o.singh@intel.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Patches Audio <patches.audio@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Vinod Koul <vinod.koul@intel.com>,
Mark Brown <broonie@kernel.org>
Subject: Applied "ASoC: Intel: Skylake: Fix missing sentinel in sst_acpi_mach" to the asoc tree
Date: Fri, 13 Oct 2017 20:25:45 +0100 [thread overview]
Message-ID: <E1e35ab-0006NM-VH@debutante> (raw)
In-Reply-To: <20171009055032.12158-4-guneshwor.o.singh@intel.com>
The patch
ASoC: Intel: Skylake: Fix missing sentinel in sst_acpi_mach
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
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
>From 364497aca1f5fdf220bd314e0550881b97d2f0fc Mon Sep 17 00:00:00 2001
From: Guneshwor Singh <guneshwor.o.singh@intel.com>
Date: Mon, 9 Oct 2017 11:20:32 +0530
Subject: [PATCH] ASoC: Intel: Skylake: Fix missing sentinel in sst_acpi_mach
To make it consistent, add sentinel for sst_cnl_devdata also.
Signed-off-by: Guneshwor Singh <guneshwor.o.singh@intel.com>
Acked-By: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
sound/soc/intel/skylake/skl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/intel/skylake/skl.c b/sound/soc/intel/skylake/skl.c
index 143ade31562f..4abbd90e394c 100644
--- a/sound/soc/intel/skylake/skl.c
+++ b/sound/soc/intel/skylake/skl.c
@@ -1011,6 +1011,7 @@ static const struct sst_acpi_mach sst_cnl_devdata[] = {
.fw_filename = "intel/dsp_fw_cnl.bin",
.pdata = &cnl_pdata,
},
+ {}
};
/* PCI IDs */
--
2.14.1
next prev parent reply other threads:[~2017-10-13 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 5:50 [PATCH 0/3] ASoC: Intel: Skylake: Add support for loading FE dais from topology Guneshwor Singh
2017-10-09 5:50 ` [PATCH 1/3] ASoC: Intel: Skylake: Add flag to check to register " Guneshwor Singh
2017-10-13 19:25 ` Applied "ASoC: Intel: Skylake: Add flag to check to register FE dais from topology" to the asoc tree Mark Brown
2017-10-09 5:50 ` [PATCH 2/3] ASoC: Intel: Skylake: Add dai load ops for dais from topology Guneshwor Singh
2017-10-13 19:25 ` Applied "ASoC: Intel: Skylake: Add dai load ops for dais from topology" to the asoc tree Mark Brown
2017-10-09 5:50 ` [PATCH 3/3] ASoC: Intel: Skylake: Fix missing sentinel in sst_acpi_mach Guneshwor Singh
2017-10-13 19:25 ` Mark Brown [this message]
2017-10-13 9:22 ` [PATCH 0/3] ASoC: Intel: Skylake: Add support for loading FE dais from topology Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1e35ab-0006NM-VH@debutante \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=guneshwor.o.singh@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox