[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTin-KSVcG2cQfRM3Ys0_g_uJVruDMw@mail.gmail.com>
Date: Fri, 3 Jun 2011 11:04:52 -0600
From: Grant Likely <grant.likely@...retlab.ca>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
alsa-devel@...a-project.org, Dmitry Artamonow <mad_soft@...ox.ru>,
x86@...nel.org, LKML <linux-kernel@...r.kernel.org>,
linux-next@...r.kernel.org, Harald Welte <laforge@...fiish.org>
Subject: Re: [PATCH] gpio: add GPIOF_ values regardless on kconfig settings
On Fri, May 27, 2011 at 2:12 PM, Grant Likely <grant.likely@...retlab.ca> wrote:
> On Fri, May 27, 2011 at 10:46:57AM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@...cle.com>
>>
>> Make GPIOF_ defined values available even when GPIOLIB nor GENERIC_GPIO
>> is enabled by moving them to <linux/gpio.h>.
>>
>> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
>
> Applied, thanks.
Hi Randy,
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
breaking on these symbols depend on GPIOLIB. Platforms not using
gpiolib are strongly discouraged now anyways, and there only a handful
of files in drivers/ that reference GPIOF_*.
g.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists