From: "David S. Miller" <davem@redhat.com>
To: muizelaar@rogers.com
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH] post-sysfs netdev cleanup
Date: Thu, 22 May 2003 17:44:15 -0700 (PDT) [thread overview]
Message-ID: <20030522.174415.28799441.davem@redhat.com> (raw)
In-Reply-To: <3ECD6E2D.5090000@rogers.com>
From: Jeff Muizelaar <muizelaar@rogers.com>
Date: Thu, 22 May 2003 20:41:17 -0400
The attached patch removes the struct device from struct net_device
and sets net_device.class_dev.dev directly.
The class_dev memset is removed because all of struct net_device
should already be memset to 0 or there will be other problems.
Looks fine to me, Stephen?
next prev parent reply other threads:[~2003-05-23 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 0:41 [PATCH] post-sysfs netdev cleanup Jeff Muizelaar
2003-05-23 0:44 ` David S. Miller [this message]
[not found] ` <3ECEB317.5020407@osdl.org>
2003-05-26 2:24 ` David S. Miller
2003-05-27 16:51 ` Stephen Hemminger
2003-05-28 8:33 ` David S. Miller
2003-05-26 2:22 ` David S. Miller
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=20030522.174415.28799441.davem@redhat.com \
--to=davem@redhat.com \
--cc=muizelaar@rogers.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).