All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: mengdong.lin@linux.intel.com
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
	mengdong.lin@intel.com, liam.r.girdwood@linux.intel.com,
	vinod.koul@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: Tue, 17 Jan 2017 17:56:36 +0000	[thread overview]
Message-ID: <20170117175636.laoybapp7jqtpzno@sirena.org.uk> (raw)
In-Reply-To: <7d5a432b03df6298e85b2af1f520e48821ada648.1484381178.git.mengdong.lin@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 324 bytes --]

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?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2017-01-17 17:56 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 [this message]
2017-01-18 16:44     ` Vinod Koul
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=20170117175636.laoybapp7jqtpzno@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.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 \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.