Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: "Lin, Mengdong" <mengdong.lin@intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	"Koul, Vinod" <vinod.koul@intel.com>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Packages 1.0.30 - release pending
Date: Thu, 5 Nov 2015 21:07:11 +0800	[thread overview]
Message-ID: <563B547F.6050206@linux.intel.com> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F84B879250@shsmsx102.ccr.corp.intel.com>



On 11/05/2015 11:08 AM, Lin, Mengdong wrote:
>> -----Original Message-----
>> From: Liam Girdwood [mailto:liam.r.girdwood@linux.intel.com]
>> Sent: Thursday, November 05, 2015 12:17 AM
>> To: Jaroslav Kysela
>> Cc: Lin, Mengdong; Takashi Iwai; Koul, Vinod; ALSA development
>> Subject: Re: [alsa-devel] Packages 1.0.30 - release pending
>>
>> On Wed, 2015-11-04 at 15:29 +0100, Jaroslav Kysela wrote:
>>> Dne 28.10.2015 v 16:06 Lin, Mengdong napsal(a):
>>>
>>>> I expect the other kernel and user space patches will be submitted next week
>> after the internal review.
>>>
>>> Any progress for the user space? If I don't receive the updates for
>>> the user space packages until Friday CEST morning, I'll release 1.1.0
>>> without them. We can release 1.1.1 quickly when all things are
>>> finished for the topology code. The distributions can adapt to new
>>> tools (like
>>> alsatplg) in 1.1.0 and then just receive the updated code (1.1.1).
>>>
>>
>> It's all going through internal review and testing now. Mengdong can probably
>> post to the list tomorrow if all is OK, otherwise we can go for 1.1.1.
>
> I think it's better to go for 1.1.1. The internal review is just ongoing.


I've sent out the alsa-lib patches for topology ABI update after the 
internal review. The thread name is "topology: Align ABI with kernel to 
version 4". Please help to review and evaluate if it's ok for this 1.1.0 
release.

All ABI updates have been merged in sound kernel except this one: 
topology: ABI - Rename dai_elems to pcm_elems in manifest
This patch is still in ASoC kernel, topic/topology branch.

Thanks
Mengdong

      parent reply	other threads:[~2015-11-05 12:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11 19:08 Packages 1.0.30 - release pending Jaroslav Kysela
2015-10-12  8:24 ` Takashi Iwai
2015-10-12  8:56   ` Koul, Vinod
2015-10-12  9:51     ` Jaroslav Kysela
2015-10-12  9:23   ` Liam Girdwood
2015-10-27 15:16   ` Takashi Iwai
2015-10-27 15:27     ` Liam Girdwood
2015-10-27 16:01       ` Jaroslav Kysela
2015-10-27 16:40         ` Liam Girdwood
2015-10-29  1:23         ` Vinod Koul
2015-10-28 15:06       ` Lin, Mengdong
2015-11-04 14:29         ` Jaroslav Kysela
2015-11-04 16:17           ` Liam Girdwood
2015-11-05  3:08             ` Lin, Mengdong
2015-11-05 13:04               ` Mengdong Lin
2015-11-05 13:12                 ` Jaroslav Kysela
2015-11-05 13:18                   ` Takashi Iwai
2015-11-05 13:33                     ` Jaroslav Kysela
2015-11-05 13:38                       ` Takashi Iwai
2015-11-05 14:43                   ` Lin, Mengdong
2015-11-05 13:07               ` Mengdong Lin [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=563B547F.6050206@linux.intel.com \
    --to=mengdong.lin@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox