From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: About to tag 2.6.23-omap1 Date: Tue, 23 Oct 2007 10:40:00 -0700 Message-ID: <20071023174000.GH5193@atomide.com> References: <20071023011920.GL17318@atomide.com> <9c9fda240710221845y341a5cb0i50b7e07e6d959853@mail.gmail.com> <471E1377.401@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <471E1377.401@googlemail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: Dirk Behme Cc: linux-omap-open-source@linux.omap.com, Kyungmin Park List-Id: linux-omap@vger.kernel.org * Dirk Behme [071023 08:30]: > Kyungmin Park wrote: >> There is a pending patch related with OMAP2 USB device DMA support. >> I think now there's one user to use this feature, Apollon. >> As David's comment, it has board specific code. >> but the DMA patch don't update the board specific code. it only adds >> the DMA codes. >> So if you don't mind I hope to merge this one too. > > Looking into my pending patches list, I think you mean > > http://linux.omap.com/pipermail/linux-omap-open-source/2007-October/011579.html > > ? Let's plan on pushing that over after updating to current mainline kernel. That way if it breaks stuff for non-DMA configurations :) >> On 10/23/07, Tony Lindgren wrote: >>> Hi all, >>> >>> I'm planning to tag 2.6.23-omap1 tomorrow morning PST with current >>> linux-omap git tree unless somebody comes up with fixes that still >>> should go in. >>> >>> So only fixes right now please, then let's update the tree to >>> mainline kernel, and try to get most of the pending patches such as >>> mmc, v4l, osk-2420, omap2-nand etc applied (and fixed if needed). >>> >>> After that, let's plan on doing the move of arch/arm/plat-omap/dsp >>> to drivers/dsp/omap. And then we prepare patches do the fixes needed >>> for Russell for plat-omap and mach-omap1 before 2.6.24-rc5 to try to >>> get them mostly in sync with mainline. Then we can hopefully sync up >>> mach-omap2 for 2.6.25-rc5. I've tagged v2.6.23-omap1 and posted the patch to usual location. Tony