All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC fixes for v4.9
Date: Fri, 04 Nov 2016 21:13:28 +0100	[thread overview]
Message-ID: <s5hfun70zrr.wl-tiwai@suse.de> (raw)
In-Reply-To: <20161104184113.p6nvwvdxr4gehwbn@sirena.org.uk>

On Fri, 04 Nov 2016 19:41:13 +0100,
Mark Brown wrote:
> 
> The following changes since commit a909d3e636995ba7c349e2ca5dbb528154d4ac30:
> 
>   Linux 4.9-rc3 (2016-10-29 13:52:02 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v4.9-rc3
> 
> for you to fetch changes up to 0b203d699e08424288b5f3eab1347143dd5d1e68:
> 
>   Merge remote-tracking branch 'asoc/fix/topology-abi' into asoc-linus (2016-11-04 12:34:05 -0600)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v4.9
> 
> The most important fix in here is a change which removes the #error
> making the topology API unusable as-is since we have recently discovered
> some production uses on Chromebooks so need to acknowledge that what
> we've got there now is an ABI.
> 
> There's also a very big batch of driver specific fixes here which have
> kept on being delayed due to more arriving so the update is another of
> these bigger than I would like ones.  There is one especially big one in
> there, for the Qualcomm code which fixes simultaneous playback and
> capture which was broken during the merge window.  The diff for that is
> large because it moves blocks of code to different functions but it's
> functionally fairly simple and if it breaks it should have been very
> obvious in testing.

Pulled now.  Thanks.


Takashi

      reply	other threads:[~2016-11-04 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 18:41 [GIT PULL] ASoC fixes for v4.9 Mark Brown
2016-11-04 20:13 ` 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=s5hfun70zrr.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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.