Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de, fulup.arfoll@iot.bzh
Subject: Re: [PATCH 0/3] ALSA: control: delegate TLV eventing to each driver
Date: Thu, 24 Aug 2017 09:17:16 +0200	[thread overview]
Message-ID: <s5h1so1v3ib.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170824014616.28859-1-o-takashi@sakamocchi.jp>

On Thu, 24 Aug 2017 03:46:13 +0200,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> This patchse is the same one which I posted and for merge to upstream.
> 
> [alsa-devel] [RFC][PATCH 0/3] ALSA: control: delegate TLV eventing to each driver
> http://mailman.alsa-project.org/pipermail/alsa-devel/2017-August/124382.html
> 
> Nothing changed from the original one.
> 
> 
> Takashi Sakamoto (3):
>   ALSA: control: delegate TLV eventing to each driver
>   ALSA: control: queue TLV event for a set of user-defined element
>   ALSA: control: TLV data is unavailable at initial state of
>     user-defined element set

Applied all three patches.  Thanks.


Takashi

      parent reply	other threads:[~2017-08-24  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24  1:46 [PATCH 0/3] ALSA: control: delegate TLV eventing to each driver Takashi Sakamoto
2017-08-24  1:46 ` [PATCH 1/3] " Takashi Sakamoto
2017-08-24  1:46 ` [PATCH 2/3] ALSA: control: queue TLV event for a set of user-defined element Takashi Sakamoto
2017-08-24  1:46 ` [PATCH 3/3] ALSA: control: TLV data is unavailable at initial state of user-defined element set Takashi Sakamoto
2017-08-24  7:17 ` 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=s5h1so1v3ib.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=fulup.arfoll@iot.bzh \
    --cc=o-takashi@sakamocchi.jp \
    /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