Re: where is device_get_parent function defined

on 22/09/2009 23:44 Stefan Ehmann said the following:
> On Tuesday 22 September 2009 16:21:54 Barney Cordoba wrote:
>> --- On Tue, 9/22/09, pluknet <pluknet_at_gmail.com> wrote:
> ...
>>> Following style(9):
>>> ###
>>>      The function type should be on a
>>> line by itself preceding the function.
>>>
>>>      static char *
>>>      function(int a1, int a2, float fl,
>>> int a4)
>>> ###
>>>
>>> So you can safely use the caret sign in regex: grep
>>> ^keyword path
>> Except for the 50K recursive warnings from the module build directories
>> you're correct.
> 
> In that case, I normally use:
> find /usr/src/ -type f | xargs grep ^device_get_parent
> 
> Additionally specifying -name '*.c' should even be faster.
> 

I am surprised with this whole 'recursive' issue because in a clean source tree
there are no recursive symlinks. They only come to be if a developer forgets to
run 'make obj' before doing 'make' in modules directories.
I think that it is a good practice to never pollute the source tree with build
objects, they should belong to /usr/obj or equivalent.

-- 
Andriy Gapon