Hi, this may be a stupid question. As I look around the kernel and driver source code I often find it difficult to find the "real" instance of a function. e.g. if I use grep to find occurrences of say "gpio_request", I get a long list to search through, but I know many of the files are not even compiled into my build. Is there an easy way to find the real place where a function is coded for my particular build? This also applies to usage - say I want to find some example of the use "gpio_request" in my particular configuration so I can copy it to save time or even to know that it is even used in my configuration. Is there a quick and easy way to do this? Many thanks and sorry for the footer (my company won't remove it - I may have to migrate to my own personal e-mail account to get around this unless someone out there has a suggestion, other than hitting the IT guy over the head, that is).
This electronic transmission is strictly confidential and intended solely for the addressee(s). If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this email. If you have received this email in error please notify the sender as soon as possible. Any views expressed within this email may not necessarily be the views held by Calrec Audio Ltd. Calrec Audio Ltd have taken measures to ensure this email is free from computer viruses, however it is recommended that you also employ anti-virus measures on your computer systems. Calrec Audio Ltd. Registered in England. Registration number: 02392336. WEEE registration number: WEE/JE0051TQ/PRO. Registered address: Nutclough Mill, Hebden Bridge, West Yorks, HX7 8EZ.
_______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
