From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v4 0/5] ALSA - hda: Add support for link audio time reporting
Date: Mon, 8 Aug 2016 10:01:53 +0530 [thread overview]
Message-ID: <20160808043153.GO9681@localhost> (raw)
In-Reply-To: <s5hlh0b5s8r.wl-tiwai@suse.de>
On Fri, Aug 05, 2016 at 02:12:52PM +0200, Takashi Iwai wrote:
> On Thu, 04 Aug 2016 12:15:59 +0200,
> Vinod Koul wrote:
>
> Looks good, but I'm going to apply it for 4.9, as the 4.8 merge window
> already started and closed soon.
Sound perfectly okay to me :-)
Let me know when you push it out.
--
~Vinod
prev parent reply other threads:[~2016-08-08 4:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 10:15 [PATCH v4 0/5] ALSA - hda: Add support for link audio time reporting Vinod Koul
2016-08-04 10:16 ` [PATCH v4 1/5] ALSA: hda - move bus_parse_capabilities to core Vinod Koul
2016-08-09 12:44 ` Applied "ALSA: hda - move bus_parse_capabilities to core" to the asoc tree Mark Brown
2016-08-04 10:16 ` [PATCH v4 2/5] ALSA: convert users to core bus_parse_capabilities Vinod Koul
2016-08-04 10:16 ` [PATCH v4 3/5] ALSA - Ext hda: remove bus_parse_capabilities Vinod Koul
2016-08-04 10:16 ` [PATCH v4 4/5] ALSA - hda: Add support for parsing new HDA capabilities Vinod Koul
2016-08-09 12:44 ` Applied "ALSA - hda: Add support for parsing new HDA capabilities" to the asoc tree Mark Brown
2016-08-04 10:16 ` [PATCH v4 5/5] ALSA - hda: Add support for link audio time reporting Vinod Koul
2016-08-09 12:44 ` Applied "ALSA - hda: Add support for link audio time reporting" to the asoc tree Mark Brown
2016-08-05 12:12 ` [PATCH v4 0/5] ALSA - hda: Add support for link audio time reporting Takashi Iwai
2016-08-05 12:16 ` Mark Brown
2016-08-05 12:26 ` Takashi Iwai
2016-08-09 7:00 ` Takashi Iwai
2016-08-10 3:05 ` Vinod Koul
2016-08-08 4:31 ` Vinod Koul [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=20160808043153.GO9681@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
/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).