Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934121Ab3CMSBN (ORCPT ); Wed, 13 Mar 2013 14:01:13 -0400 Received: from mail-ie0-f170.google.com ([209.85.223.170]:39161 "EHLO mail-ie0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933095Ab3CMSBI (ORCPT ); Wed, 13 Mar 2013 14:01:08 -0400 MIME-Version: 1.0 In-Reply-To: References: <1363083150-30964-1-git-send-email-acourbot@nvidia.com> Date: Wed, 13 Mar 2013 19:01:07 +0100 Message-ID: Subject: Re: [RFC 00/17] Remove GENERIC_GPIO from architecture code From: Linus Walleij To: Grant Likely Cc: Alexandre Courbot , Arnd Bergmann , Russell King , Haavard Skinnemoen , Hans-Christian Egtvedt , Mike Frysinger , Geert Uytterhoeven , Ralf Baechle , Jonas Bonn , Josh Boyer , Matt Porter , Benjamin Herrenschmidt , Paul Mackerras , Kumar Gala , Vitaly Bordug , Marcelo Tosatti , Paul Mundt , Guan Xuetao , Chris Zankel , Max Filippov , Alexandre Courbot , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1036 Lines: 25 On Wed, Mar 13, 2013 at 8:53 AM, Grant Likely wrote: > On Wed, Mar 13, 2013 at 1:12 PM, Linus Walleij wrote: >> On Tue, Mar 12, 2013 at 11:12 AM, Alexandre Courbot wrote: >> >>> This series makes sure the GENERIC_GPIO option can only be set through GPIOLIB >>> (and not by individual architectures), as a first step towards its removal. >> >> Nice! >> Acked-by: Linus Walleij >> >> I bet something will break, anyway: no pain no gain. > > Since this is a pretty invasive patch series that touches a lot of > architectures, we should get it into a separate branch that can get > pulled into linux-next. Good point. Alexandre, do you have a git repo to attain this? Yours, Linus Walleij -- 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/