Re: where is device_get_parent function defined

From: Gary Jennejohn <gary.jennejohn_at_freenet.de>
Date: Tue, 22 Sep 2009 17:16:29 +0200
On Tue, 22 Sep 2009 17:37:00 +0400
pluknet <pluknet_at_gmail.com> wrote:

> 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
> 

Which, of course, is exactly why I used it.  This style(9) rule is one
big advantage which FreeBSD has over Linux.  It's practically impossible to
find a function in Linux because the type is always on the same line as the
function declaration.  Drives my crazy.

---
Gary Jennejohn
Received on Tue Sep 22 2009 - 13:16:31 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC