Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753659Ab1FOAEA (ORCPT ); Tue, 14 Jun 2011 20:04:00 -0400 Received: from rcsinet10.oracle.com ([148.87.113.121]:39556 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752428Ab1FOAD6 (ORCPT ); Tue, 14 Jun 2011 20:03:58 -0400 Date: Tue, 14 Jun 2011 17:03:21 -0700 From: Randy Dunlap To: Grant Likely Cc: Mark Brown , Stephen Rothwell , alsa-devel@alsa-project.org, Dmitry Artamonow , x86@kernel.org, LKML , linux-next@vger.kernel.org, Harald Welte Subject: Re: [PATCH] gpio: add GPIOF_ values regardless on kconfig settings Message-Id: <20110614170321.10e1caa7.randy.dunlap@oracle.com> In-Reply-To: <20110614161357.GB1839@ponder.secretlab.ca> References: <4DDB3AFF.9030006@oracle.com> <20110524075248.GB19734@sirena.org.uk> <20110527074552.GA907@ponder.secretlab.ca> <4DDFE391.2030507@oracle.com> <20110527201201.GA6645@ponder.secretlab.ca> <20110603171837.GA9918@opensource.wolfsonmicro.com> <4DEC4D67.6010506@oracle.com> <20110614091211.465553de.randy.dunlap@oracle.com> <20110614161357.GB1839@ponder.secretlab.ca> Organization: Oracle Linux Eng. X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Source-IP: rtcsinet21.oracle.com [66.248.204.29] X-CT-RefId: str=0001.0A090208.4DF7F6D8.0019:SCFSTAT5015188,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2687 Lines: 59 On Tue, 14 Jun 2011 10:13:57 -0600 Grant Likely wrote: > On Tue, Jun 14, 2011 at 09:12:11AM -0700, Randy Dunlap wrote: > > On Sun, 05 Jun 2011 20:45:43 -0700 Randy Dunlap wrote: > > > > > On 06/03/11 10:42, Grant Likely wrote: > > > > On Fri, Jun 3, 2011 at 11:18 AM, Mark Brown > > > > wrote: > > > >> On Fri, Jun 03, 2011 at 11:04:52AM -0600, Grant Likely wrote: > > > >> > > > >>> I ended up not pushing this one to Linus. Turns out it causes other > > > >>> breakage on other platforms that don't include include/linux/gpio.h. > > > >>> Since I don't have confidence that I'll be able to find all the > > > >>> offenders, I'm dropping it. I recommend making any drivers that are > > > >> > > > >> So, this originally came about because I pushed back on adding random > > > >> dependencies like this for features which are pretty much optional in > > > >> drivers - their use of GPIOs is totally optional and the dependencies > > > >> are just too fragile, leading to noise with all the randconfigs. It > > > >> seems better to get the architectures to keep up with enhancements to > > > >> gpiolib (or convert to it) than to have to worry about this in drivers. > > > > > > > > Fair enough. Randy, if you or someone else can check that all GPIOF_ > > > > users have the required #include , then I'm okay with > > > > this patch. > > > > > > OK, I'll look at that. > > > > Of the 70 files that use GPIOF_ macros: > > > > hdr missing in: ./arch/arm/mach-pxa/spitz_pm.c > > hdr missing in: ./arch/avr32/mach-at32ap/pio.c > > hdr missing in: ./arch/avr32/mach-at32ap/include/mach/portmux.h > > hdr missing in: ./arch/avr32/boards/hammerhead/setup.c > > hdr missing in: ./arch/avr32/boards/hammerhead/flash.c > > hdr missing in: ./arch/avr32/boards/mimc200/setup.c > > hdr missing in: ./arch/avr32/boards/atstk1000/setup.c > > hdr missing in: ./drivers/pcmcia/pxa2xx_vpac270.c > > > > > > > Do you have any examples of builds that failed with this patch? > > > > and would you merge patch(es) that add this header file to those source > > files? If not, I'll need to make 3 separate patches for them. That list of files above is incorrect. Bad grep pattern. Drop all of the avr32 files. Ending patch is small -- sending it soon. > Yes I would. I'm fine with it all being one patch. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- 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/