From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [GIT PULL] ASoC fixes for v4.9 Date: Fri, 04 Nov 2016 21:13:28 +0100 Message-ID: References: <20161104184113.p6nvwvdxr4gehwbn@sirena.org.uk> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 82F422674C0 for ; Fri, 4 Nov 2016 21:13:29 +0100 (CET) In-Reply-To: <20161104184113.p6nvwvdxr4gehwbn@sirena.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: alsa-devel@alsa-project.org, Liam Girdwood List-Id: alsa-devel@alsa-project.org 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