Date: Wed, 23 Sep 2009 15:00:05 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Stefan Ehmann <shoesoft@gmx.net> Cc: Barney Cordoba <barney_cordoba@yahoo.com>, freebsd-current@freebsd.org, pluknet <pluknet@gmail.com> Subject: Re: where is device_get_parent function defined Message-ID: <4ABA0DC5.6070502@icyb.net.ua> In-Reply-To: <200909222244.23901.shoesoft@gmx.net> References: <654636.94077.qm@web63908.mail.re1.yahoo.com> <200909222244.23901.shoesoft@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ABA0DC5.6070502>