Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932110AbZAPKKQ (ORCPT ); Fri, 16 Jan 2009 05:10:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758048AbZAPKJ5 (ORCPT ); Fri, 16 Jan 2009 05:09:57 -0500 Received: from mail.gmx.net ([213.165.64.20]:56770 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1758309AbZAPKJz (ORCPT ); Fri, 16 Jan 2009 05:09:55 -0500 X-Authenticated: #20450766 X-Provags-ID: V01U2FsdGVkX19jdfVIRNpj+W9X3kwvAVczyP65/5BTDjSIMeejJ6 owCKQLCDH0kE/a Date: Fri, 16 Jan 2009 11:09:54 +0100 (CET) From: Guennadi Liakhovetski To: Dan Williams cc: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com, Sascha Hauer , linux-arm-kernel@lists.arm.linux.org.uk, Geert Uytterhoeven Subject: Re: [PATCH 0/4 v6] i.MX31: dmaengine and framebuffer drivers In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Y-GMX-Trusted: 0 X-FuHaFi: 0.5600000000000001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1797 Lines: 43 On Mon, 5 Jan 2009, Dan Williams wrote: > On Fri, Dec 26, 2008 at 10:11 AM, Guennadi Liakhovetski > wrote: > > Hi, > > > > This is version 6 of dmaengine and framebuffer drivers for i.MX31. > > > > Tha drivers/dma/ bits look ok to me minus the new warnings: > > drivers/dma/ipu/ipu_irq.c: In function 'ipu_irq_fn': > drivers/dma/ipu/ipu_irq.c:328: warning: 'irq' may be used > uninitialized in this function > drivers/dma/ipu/ipu_irq.c: In function 'ipu_irq_err': > drivers/dma/ipu/ipu_irq.c:290: warning: 'irq' may be used > uninitialized in this function > > I can take patches 1 and 2 through the async_tx tree, or if you would > rather, add my Acked-by to those and take 1-4 through the MXC tree. > I'll be sending the async_tx pull request for 2.6.29 in the next few > days. Ok, let's do it this way: Sascha has acked version 8 of patches 2 and 3. And there seems to be no active framebuffer maintainer ATM. So, maybe you could take patches 1-3 into your tree, so they are exposed to the public, people have easier access to them in case they want to test (I had several requests), and you update them in case you change async-tx API again:-) It would be good to try and push them in for 2.6.29 - these are new drivers, so, might still be possible to convince Andrew / Linus, if not, you could keep them in your tree (and in next) until 2.6.30, then we'd add platform bindings and the camera driver. What do you think? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/