From: Takashi Iwai <tiwai@suse.de>
To: "Yang, Libin" <libin.yang@intel.com>
Cc: "Lin, Mengdong" <mengdong.lin@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"libin.yang@linux.intel.com" <libin.yang@linux.intel.com>
Subject: Re: [RFC PATCH v3 0/3] support DP MST audio
Date: Thu, 20 Oct 2016 10:46:15 +0200 [thread overview]
Message-ID: <s5hy41jcsrs.wl-tiwai@suse.de> (raw)
In-Reply-To: <96A12704CE18D347B625EE2D4A099D194FA49B7E@SHSMSX103.ccr.corp.intel.com>
On Thu, 20 Oct 2016 09:23:57 +0200,
Yang, Libin wrote:
>
> Hi Takashi,
>
> Pandiyan, Dhinakaran has root caused the MST flicker issue. He is
> still working with gfx team to decide how to make the patch.
> The draft patch can be found:
> https://patchwork.freedesktop.org/patch/115585/
>
> BTW: Not sure if you have time to review my updated
> audio patches. Thanks.
The code changes look mostly OK through a quick glance.
Some places have minor coding style issues and more changelogs would
be required.
I'll give detailed review comments later.
thanks,
Takashi
prev parent reply other threads:[~2016-10-20 8:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 7:49 [RFC PATCH v3 0/3] support DP MST audio libin.yang
2016-10-13 7:49 ` [RFC PATCH v3 1/3] ALSA: hda - add DP mst verb support libin.yang
2016-10-20 15:27 ` Takashi Iwai
2016-10-21 6:52 ` Yang, Libin
2016-10-13 7:49 ` [RFC PATCH v3 2/3] ALSA: hda - add DP mst audio support libin.yang
2016-10-20 15:34 ` Takashi Iwai
2016-10-21 8:24 ` Yang, Libin
2016-10-21 8:43 ` Takashi Iwai
2016-10-21 8:56 ` Yang, Libin
2016-10-21 9:05 ` Takashi Iwai
2016-10-21 12:25 ` Yang, Libin
2016-10-21 12:33 ` Takashi Iwai
2016-10-21 13:25 ` Yang, Libin
2016-10-24 7:09 ` Yang, Libin
2016-10-24 8:41 ` Takashi Iwai
2016-10-24 8:52 ` Yang, Libin
2016-10-13 7:49 ` [RFC PATCH v3 3/3] ALSA: Documentation about HDA DP MST pin init and connection libin.yang
2016-10-20 7:23 ` [RFC PATCH v3 0/3] support DP MST audio Yang, Libin
2016-10-20 8:46 ` Takashi Iwai [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=s5hy41jcsrs.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=libin.yang@intel.com \
--cc=libin.yang@linux.intel.com \
--cc=mengdong.lin@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.