From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Mengdong Lin <mengdong.lin@linux.intel.com>,
vinod.koul@intel.com, mengdong.lin@intel.com,
liam.r.girdwood@linux.intel.com, pierre-louis.bossart@intel.com
Subject: Re: [PATCH v3 1/2] ASoC: core: Add API to use DMI name in sound card long name
Date: Wed, 11 Jan 2017 16:06:49 +0100 [thread overview]
Message-ID: <s5hd1fty6t2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170111150119.y43ik2xjf45xgyqr@sirena.org.uk>
On Wed, 11 Jan 2017 16:01:19 +0100,
Mark Brown wrote:
>
> On Wed, Jan 11, 2017 at 06:27:03PM +0800, Mengdong Lin wrote:
> > On 01/11/2017 04:03 PM, Takashi Iwai wrote:
> > > Mengdong Lin wrote:
> > > > On 01/10/2017 03:09 PM, Takashi Iwai wrote:
> > > > > mengdong.lin@linux.intel.com wrote:
>
> > > > > > + * Possible card long names may be:
> > > > > > + * DellInc..XPS139343.01.0310JH
> > > > > > + * ASUSTeKCOMPUTERINC..T100TA.1.0.T100TA
> > > > > > + * Circuitco.MinnowboardMaxD0PLATFORM.D0.MinnowBoardMAX
>
> > It looks nice. Thanks for the tips! I'll use "-" as the separator, and
> > convert the the existing "-" in DMI strings to "_".
>
> "nice" seems like a very strong term here :) Not sure there's any
> options that will look much better but still.
Yeah, it's still not photogenic. But the merit is rather that it
makes easier to parse.
Takashi
next prev parent reply other threads:[~2017-01-11 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 6:42 [PATCH v3 0/2] ASoC: Use DMI name in sound card long name mengdong.lin
2017-01-10 6:42 ` [PATCH v3 1/2] ASoC: core: Add API to use " mengdong.lin
2017-01-10 7:09 ` Takashi Iwai
2017-01-11 6:32 ` Mengdong Lin
2017-01-11 8:03 ` Takashi Iwai
2017-01-11 10:27 ` Mengdong Lin
2017-01-11 15:01 ` Mark Brown
2017-01-11 15:06 ` Takashi Iwai [this message]
2017-01-10 6:43 ` [PATCH v3 2/2] ASoC: Intel: Use DMI name for sound card long name in Broadwell machine driver mengdong.lin
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=s5hd1fty6t2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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=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;
as well as URLs for NNTP newsgroup(s).