From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Julien Laganier <Julien.Laganier@Sun.COM>
Cc: David CM Weber <dweber@backbonesecurity.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: device struct
Date: Wed, 25 Jul 2001 09:40:12 -0700 [thread overview]
Message-ID: <3B5EF66C.A90DAF6E@osdlab.org> (raw)
In-Reply-To: <94FD5825A793194CBF039E6673E9AFE0C017@bbserver1.backbonesecurity.com> <3B5EF43E.C9EAF2B1@Sun.COM>
Julien Laganier wrote:
>
> David CM Weber wrote:
> >
> > I'm looking at some old (circa v2.2.5 of the kernel) sample code,
> > referring to the networking system. It refers to a structure named
> > "device". Was this replaced with something else?
> >
> > On a similar note, is there a "good" way of finding this data myself?
> > I've been using ctags, and this is of limited use. (Sometimes good,
> > sometimes bad).
> >
>
> Use CSCOPE, available at http://cscope.sourceforge.net
> It's very usefull !
I agree that cscope is useful, but the simple answer to David's
question is that struct device was replaced with struct net_device
in 2.4 so that the more generic struct device could be used for
more generic purposes.
~Randy
prev parent reply other threads:[~2001-07-25 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 15:44 device struct David CM Weber
2001-07-25 16:30 ` Julien Laganier
2001-07-25 16:40 ` Randy.Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B5EF66C.A90DAF6E@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=Julien.Laganier@Sun.COM \
--cc=dweber@backbonesecurity.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox