From: Takashi Iwai <tiwai@suse.de>
To: "Yang, Libin" <libin.yang@intel.com>
Cc: "Lin, Mengdong" <mengdong.lin@intel.com>,
"libin.yang@linux.intel.com" <libin.yang@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: hda - hdmi create spdif ctl based on pcm
Date: Fri, 15 Jan 2016 06:51:37 +0100 [thread overview]
Message-ID: <s5hoacnl79y.wl-tiwai@suse.de> (raw)
In-Reply-To: <96A12704CE18D347B625EE2D4A099D19046569BB@SHSMSX103.ccr.corp.intel.com>
On Fri, 15 Jan 2016 01:46:37 +0100,
Yang, Libin wrote:
>
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Thursday, January 14, 2016 5:09 PM
> > To: libin.yang@linux.intel.com
> > Cc: alsa-devel@alsa-project.org; Lin, Mengdong; Yang, Libin
> > Subject: Re: [PATCH] ALSA: hda - hdmi create spdif ctl based on pcm
> >
> > On Thu, 14 Jan 2016 08:49:46 +0100,
> > libin.yang@linux.intel.com wrote:
> > >
> > > From: Libin Yang <libin.yang@linux.intel.com>
> > >
> > > SPDIF ctl should be based on pcm. Each spdif ctl controls
> > > one pcm state.
> > >
> > > This patch creates spdif based on pcm and no longer
> > > based on pin.
> >
> > Which branch is this supposed to be applied to? I thought it's for
> > MST, then this isn't for 4.5.
> >
> > If it's for MST, please postpone it until the merge window is closed.
> > If this isn't for 4.5, please clarify why this has to be applied.
>
> It's for MST. I will submit it later. When should I submit the patch?
After the merge window is closed.
Takashi
next prev parent reply other threads:[~2016-01-15 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 7:49 [PATCH] ALSA: hda - hdmi create spdif ctl based on pcm libin.yang
2016-01-14 9:08 ` Takashi Iwai
2016-01-15 0:46 ` Yang, Libin
2016-01-15 5:51 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-29 5:53 libin.yang
2016-01-29 5:59 ` Yang, Libin
2016-01-29 6:38 ` Takashi Iwai
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=s5hoacnl79y.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.