where is device_get_parent function defined

[Barney Cordoba]

--- On Tue, 9/22/09, pluknet <pluknet at gmail.com> wrote:

> From: pluknet <pluknet at gmail.com>
> Subject: Re: where is device_get_parent function defined
> To: "Barney Cordoba" <barney_cordoba at yahoo.com>
> Cc: current at freebsd.org
> Date: Tuesday, September 22, 2009, 9:37 AM
> 2009/9/22 Barney Cordoba <barney_cordoba at yahoo.com>:
> >
> >
> > --- On Tue, 9/22/09, Gary Jennejohn <gary.jennejohn at freenet.de>
> wrote:
> >
> >> From: Gary Jennejohn <gary.jennejohn at freenet.de>
> >> Subject: Re: where is device_get_parent function
> defined
> >> To: "Barney Cordoba" <barney_cordoba at yahoo.com>
> >> Cc: current at freebsd.org
> >> Date: Tuesday, September 22, 2009, 5:32 AM
> >> On Mon, 21 Sep 2009 15:27:42 -0700
> >> (PDT)
> >> Barney Cordoba <barney_cordoba at yahoo.com>
> >> wrote:
> >>
> >> > I can't seem to find where
> device_get_parent() is
> >> defined.
> >> >
> >>
> >> /sys/kern/subr_bus,c
> >>
> >> grep -r ^device_get_parent /sys/
> >
> > Thanks, I found it shortly after posting. The
> "problem" with grep is
> > that you get about a billion lines, particularly on
> systems with 4 or
> > 5 different kernel sources installed.
> >
> 
> 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
> 
> -- 
> wbr,
> pluknet

Except for the 50K recursive warnings from the module build directories
you're correct.

I'd think there would be an automated way to add the source modules into
the man pages. It certainly would be useful.

BC