From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Daniel Drake <drake@endlessm.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: snd_soc_set_dmi_name - Shouldn't it use SYS_VENDOR?
Date: Tue, 2 May 2017 18:19:32 +0800 [thread overview]
Message-ID: <59085D34.2070604@linux.intel.com> (raw)
In-Reply-To: <CAD8Lp46A9oDMTabXuMPutMtP5Fkbgc4HXVwtNj2dbrrSDe+bUA@mail.gmail.com>
On 04/29/2017 11:27 PM, Daniel Drake wrote:
> Hi,
>
> On Fri, Apr 28, 2017 at 10:21 AM, Lin, Mengdong <mengdong.lin@intel.com> wrote:
>> I just submitted a patch to fix this http://mailman.alsa-project.org/pipermail/alsa-devel/2017-April/120271.html
>> It passed building and I will test it next Tuesday. 3 Intel machines may have null DMI_SYS_VENDOR.
>
> Thanks! I tested the patch on my platform here, and it is working
> correctly, I now get the expected vendor name appearing in the string.
>
> Daniel
> _______________________________________________
Many thanks for testing on your platforms! It also works on my
platforms today.
Regards
Mengdong
prev parent reply other threads:[~2017-05-02 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 18:00 snd_soc_set_dmi_name - Shouldn't it use SYS_VENDOR? Daniel Drake
2017-04-27 19:28 ` Pierre-Louis Bossart
2017-04-27 20:13 ` Daniel Drake
2017-04-27 20:32 ` Pierre-Louis Bossart
2017-04-27 21:02 ` Daniel Drake
2017-04-28 8:36 ` Takashi Iwai
2017-04-28 10:35 ` Liam Girdwood
2017-04-28 15:02 ` Lin, Mengdong
2017-04-28 16:21 ` Lin, Mengdong
2017-04-29 15:27 ` Daniel Drake
2017-05-02 10:19 ` Mengdong Lin [this message]
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=59085D34.2070604@linux.intel.com \
--to=mengdong.lin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=drake@endlessm.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=pierre-louis.bossart@linux.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).