lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201110112222.24646.heiko@sntech.de>
Date:	Tue, 11 Oct 2011 22:22:24 +0200
From:	Heiko Stübner <heiko@...ech.de>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lrg@...com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: linux-next: Tree for Oct 11 (gpio regulator)

Hi Randy,

Am Dienstag 11 Oktober 2011, 21:32:11 schrieb Randy Dunlap:
> On 10/11/11 02:11, Stephen Rothwell wrote:
> > Hi all,
> > 
> > The linux-next tree is now available from
> > git://github.com/sfrothwell/linux-next.git as a temporary measure while
> > the kernel.org servers are unavailable.
> > 
> > It may also turn up on git.kernel.org (depending on the mirroring).  The
> > patch set is still absent, however.
> > 
> > Changes since 20111007:
> > 
> > The gpio tree still has its build failure so I used the version from
> > next-20111005.
> 
> (maybe fixed there?)
> (i386 build)
> 
> drivers/regulator/gpio-regulator.c:121:3: error: invalid use of undefined
> type 'struct gpio' drivers/regulator/gpio-regulator.c:121:29: error:
> dereferencing pointer to incomplete type
> drivers/regulator/gpio-regulator.c:191:32: error: invalid application of
> 'sizeof' to incomplete type 'struct gpio'
> drivers/regulator/gpio-regulator.c:281:3: error: invalid use of undefined
> type 'struct gpio' drivers/regulator/gpio-regulator.c:281:20: error:
> dereferencing pointer to incomplete type
> 
> (GPIOLIB is not enabled.)
> Full randconfig file is attached.

thanks for catching this.

I would guess the Kconfig entry of the gpio-regulator needs a
		"depends on GENERIC_GPIO"
as it won't be able to function without gpiolib - correct?

Heiko
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ