alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: [alsa-devel] [PATCH 0/2] ASoC: Follow the recent ALSA core API changes
Date: Thu, 21 Nov 2019 20:07:07 +0100	[thread overview]
Message-ID: <20191121190709.29121-1-tiwai@suse.de> (raw)

Hi,

this is a follow-up patch set for ASoC to adapt the recent ALSA PCM
core changes.  It's merely a preliminary and this itself doesn't
change the current driver behavior.  The purpose of this submission is
to get the basic API changes done in 5.5-rc1, so that other trees can
apply the actual changes later individually.  The actual cleanups and
changes in the driver side will be submitted after 5.5 merge window.

Mark, if you are OK with this, please give ACK.  Then I'll merge them
into my tree for 5.5-rc1.


thanks,

Takashi

===

Takashi Iwai (2):
  ASoC: pcm: Make ioctl ops optional
  ASoC: component: Add sync_stop PCM ops

 include/sound/soc-component.h |  3 +++
 sound/soc/soc-component.c     | 19 +++++++++++++++++++
 sound/soc/soc-pcm.c           |  6 ++++--
 3 files changed, 26 insertions(+), 2 deletions(-)

-- 
2.16.4

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

             reply	other threads:[~2019-11-21 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 19:07 Takashi Iwai [this message]
2019-11-21 19:07 ` [alsa-devel] [PATCH 1/2] ASoC: pcm: Make ioctl ops optional Takashi Iwai
2019-11-21 19:07 ` [alsa-devel] [PATCH 2/2] ASoC: component: Add sync_stop PCM ops Takashi Iwai
2019-11-22 13:34 ` [alsa-devel] [PATCH 0/2] ASoC: Follow the recent ALSA core API changes Mark Brown
2019-11-22 13:41   ` 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=20191121190709.29121-1-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    /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).