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
| ||
|
Date: Wed, 2 Jul 2008 22:00:49 -0700 From: David Brownell <david-b@...bell.net> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Michael Buesch <mb@...sch.de>, sfr@...b.auug.org.au, linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com> Subject: Re: [PATCH] gpiolib: Allow user-selection On Wednesday 02 July 2008, Andrew Morton wrote: > On Wed, 2 Jul 2008 23:46:53 +0200 > Michael Buesch <mb@...sch.de> wrote: > > > This patch adds functionality to the gpio-lib subsystem to > > make it possible to enable the gpio-lib code even if the > > architecture code didn't request to get it built in. > > drivers/gpio/gpiolib.c: In function 'gpio_export': > drivers/gpio/gpiolib.c:432: error: 'struct class' has no member named 'devices' > drivers/gpio/gpiolib.c:456: error: implicit declaration of function 'device_create' > drivers/gpio/gpiolib.c:457: warning: assignment makes pointer from integer without a cast > drivers/gpio/gpiolib.c: In function 'gpio_unexport': > drivers/gpio/gpiolib.c:509: warning: passing argument 2 of 'class_find_device' from incompatible pointer type > drivers/gpio/gpiolib.c:509: error: too few arguments to function 'class_find_device' > drivers/gpio/gpiolib.c: In function 'gpiochip_export': > drivers/gpio/gpiolib.c:536: error: 'struct class' has no member named 'devices' > drivers/gpio/gpiolib.c:542: warning: assignment makes pointer from integer without a cast > drivers/gpio/gpiolib.c: In function 'gpiochip_unexport': > drivers/gpio/gpiolib.c:575: warning: passing argument 2 of 'class_find_device' from incompatible pointer type > drivers/gpio/gpiolib.c:575: error: too few arguments to function 'class_find_device' > > I assume this patch was prepared against some ancient out-of-date > kernel such as current Linus mainline. May be, but shuffling headers around would not have caused that type of breakage. I'm thinking some driver model changes broke the gpio sysfs interface code, and this happens to show up right now because that code wasn't previously getting built. Grumph. I can easily switch the device_create() over to use device_create_drvdata() -- didn't I already send in a patch like that? -- but the other stuff is completely backwards-incompatible. - Dave > > Guys, we have a new development tree now. > -- 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