From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: PATCH[V2 1/3]: Update Platform files for SPI Date: Tue, 9 Feb 2010 15:07:10 -0800 Message-ID: <20100209230710.GL21755@atomide.com> References: <9629.10.24.255.17.1265192505.squirrel@dbdmail.itg.ti.com> <20100209222513.GJ21755@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Hemanth V , spi-devel-general@lists.sourceforge.net, linux-omap@vger.kernel.org, dbrownell@users.sourceforge.net To: Grant Likely Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-spi.vger.kernel.org * Grant Likely [100209 14:38]: > On Tue, Feb 9, 2010 at 3:25 PM, Tony Lindgren wrote: > > * Hemanth V [100203 02:19]: > >> From ee48142ddc43129a21676dbb56a83e3e7d8063de Mon Sep 17 00:00:00 2001 > >> From: Hemanth V > >> Date: Fri, 27 Nov 2009 14:22:30 +0530 > >> Subject: [PATCH] Update platform files > >> > >> This patch updates platform files for > >> fifo, slave support > >> > >> Signed-off-by: Hemanth V > > > > This should get merged via the spi-devel list with the other patches. > > > > Acked-by: Tony Lindgren > > Personally, I prefer not to carry arch/* changes in my next-spi > branch, since it means that my pull requests are less obvious for > Linus and there is greater chance of conflict. > > But if you still really want me to merge it through my tree, (or if > getting the patches out of order will break things) then I'll pick it > up. Just let me know. OK, if you ack it, I'll add the header into omap for-next. That might break git bisect for some configurations depending in which order the patches get pulled by Linus.. I guess eventually this header should not live under plat. Regards, Tony