From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: alsa-1.0.16 Date: Thu, 17 Jan 2008 17:26:21 -0600 Message-ID: <478FE41D.5040703@freescale.com> References: <1200595969.5011.104.camel@razman.gruemaster.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from de01egw02.freescale.net (de01egw02.freescale.net [192.88.165.103]) by alsa0.perex.cz (Postfix) with ESMTP id ED34524733 for ; Fri, 18 Jan 2008 00:26:26 +0100 (CET) In-Reply-To: <1200595969.5011.104.camel@razman.gruemaster.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Tobin Davis Cc: Takashi Iwai , alsa-devel@alsa-project.org, Thierry Vignaud List-Id: alsa-devel@alsa-project.org Tobin Davis wrote: > What is the cutoff for getting a patch in for new hardware? I'm working > on a project that I think we want support in 2.6.24, if alsa 1.0.16 is > going in it. 2.6.24 is almost finished. It's too late for any major additions. The next target is 2.6.25, and the window for that will be open soon (once 2.6.24 is officially announced). You better hurry up! -- Timur Tabi Linux kernel developer at Freescale