From: Takashi Iwai Subject: Re: Channel map API patches: to be 3.7 or not to be? Date: Mon, 17 Sep 2012 11:39:26 +0200 Message-ID: References: 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 (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 020CF261665 for ; Mon, 17 Sep 2012 11:39:28 +0200 (CEST) Received: from relay2.suse.de (unknown [195.135.220.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id CB248A329D for ; Mon, 17 Sep 2012 11:39:27 +0200 (CEST) In-Reply-To: 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: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Mon, 10 Sep 2012 19:43:33 +0200, Takashi Iwai wrote: > > Hi, > > does anyone have concern if I push the current channel map API patches > (in sound-unstable git tree topic/tlv-chmap branch) for linux-next, > i.e. for inclusion to 3.7 kernel? > > I don't worry too much about the kernel API. This can be refactored > later. But the kernel ABI must retain, so we won't change in an > incompatible way any longer once after it's merged to the upstream. > > So, if anyone sees a flaw in the kernel ABI definition using control > elements, let me know. > > (But note that the API can't be perfect for all generic purposes. > It's designed to be "good enough" for a big lack for multi-channel > streaming. Of course, this doesn't discourage to use the API for any > other purposes.) FYI, as I haven't got any big NO-NO, now the topic branch for chmap is merged to for-next branch. I'm going to merge user-space side, alsa-lib and alsa-utils patches. Takashi