From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, mengdong.lin@linux.intel.com,
tiwai@suse.de, mengdong.lin@intel.com,
liam.r.girdwood@linux.intel.com, pierre-louis.bossart@intel.com
Subject: Re: [PATCH v4 2/2] ASoC: Intel: Use DMI name for sound card long name in Broadwell machine driver
Date: Wed, 18 Jan 2017 22:14:59 +0530 [thread overview]
Message-ID: <20170118164459.GF3573@localhost> (raw)
In-Reply-To: <20170117175636.laoybapp7jqtpzno@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 566 bytes --]
On Tue, Jan 17, 2017 at 05:56:36PM +0000, Mark Brown wrote:
> On Sat, Jan 14, 2017 at 04:13:09PM +0800, mengdong.lin@linux.intel.com wrote:
> > From: Mengdong Lin <mengdong.lin@linux.intel.com>
> >
> > Intel Broadwell machine driver will call API snd_soc_set_dmi_name() to
> > use DMI info to make the sound card long name.
>
> I guess we'll see further patches for other machine drivers?
Yes that's the idea. At least we will convert the Skylake and Broxton ones,
after the current submitted patches and DP-MST ones are merged.
Thanks
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2017-01-18 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 8:12 [PATCH v4 0/2] ASoC: Use DMI name in sound card long name mengdong.lin
2017-01-14 8:13 ` [PATCH v4 1/2] ASoC: core: Add API to use " mengdong.lin
2017-01-17 18:45 ` Applied "ASoC: core: Add API to use DMI name in sound card long name" to the asoc tree Mark Brown
2017-01-14 8:13 ` [PATCH v4 2/2] ASoC: Intel: Use DMI name for sound card long name in Broadwell machine driver mengdong.lin
2017-01-17 17:56 ` Mark Brown
2017-01-18 16:44 ` Vinod Koul [this message]
2017-01-18 16:50 ` Takashi Iwai
2017-01-18 17:23 ` Pierre-Louis Bossart
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=20170118164459.GF3573@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=mengdong.lin@linux.intel.com \
--cc=pierre-louis.bossart@intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).