From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC 0/21 Continue phasing out legacy GPIO calls Date: Thu, 30 Oct 2008 11:21:24 -0700 Message-ID: <20081030182123.GY13227@atomide.com> References: <1225280189-6559-1-git-send-email-jarkko.nikula@nokia.com> <200810300043.07813.david-b@pacbell.net> <20081030173215.GU13227@atomide.com> <200810301116.18214.david-b@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-01-bos.mailhop.org ([63.208.196.178]:51077 "EHLO mho-01-bos.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756060AbYJ3SV3 (ORCPT ); Thu, 30 Oct 2008 14:21:29 -0400 Content-Disposition: inline In-Reply-To: <200810301116.18214.david-b@pacbell.net> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: David Brownell Cc: Jarkko Nikula , linux-omap@vger.kernel.org * David Brownell [081030 11:16]: > On Thursday 30 October 2008, Tony Lindgren wrote: > > > > Great, to me those look safe to merge. Can you Cc Russell on the > > arch/arm/*omap* patches if you merge them via gpiolib patches? > > > > Basically anything that will cause merge conflicts for omap-all > > should go via Russell so we don't frustrate him further, but > > I don't think these will cause an issue for him. > > Unless you think they should go into 2.6.28, I'll just let > you merge them via Russell for 2.6.29 ... they're almost all > arch/arm/* changes, aren't bugfixes, and don't affect non-OMAP > code, so they don't fit into one of the usual categories of > stuff Russell avoids (cross-platform or drivers/* code). OK, will queue them up for 2.6.29 then. Tony