| 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
| ||
|
Message-Id: <200703231528.10508.ngustavson@emacinc.com> Date: Fri, 23 Mar 2007 15:28:10 -0500 From: NZG <ngustavson@...cinc.com> To: linux-kernel@...r.kernel.org Subject: default functions for gpio WHY I"M ASKING THIS QUESTION: I'm implementing some gpio calls in the ep93xx arch. My problem is that gpio's are really board specific, not just mach specific. I can code the function calls into my board init, but where should these functions be prototyped? Ideally, I think the compiler should build a "default" function for int gpio_request which fails, rather than a compile error for other boards within the same arch. THE ACTUAL QUESTION: Is there a way to build a "default" function, which is compiled in if it's not defined elsewhere? Anyone know where an example of this might be lurking. Also, if this is possible, is it a good idea? thx, NZG - 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