From: Stephen Hemminger <shemminger@osdl.org>
To: Peter Johanson <latexer@gentoo.org>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: rmmodding e100 trace calls on 2.6.0-test2-mm2
Date: Fri, 1 Aug 2003 16:01:49 -0700 [thread overview]
Message-ID: <20030801160149.2392a079.shemminger@osdl.org> (raw)
In-Reply-To: <20030801224932.GA4241@gonzo.peterjohanson.com>
One of the -mm patches produces a warning which will be taken care of later when
all the network drivers are converted to dynamically allocating net_device's.
At that point, a massive patch will be needed that changes all instances of:
unregister_netdev(dev);
my cleanup...
kfree(dev); // becomes release_netdev(dev);
new release_netdev() will release the dev kobject at that point.
I have the code ready, just been waiting till all net device's converted.
Prefer not to break the world at this point.
prev parent reply other threads:[~2003-08-01 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 22:50 rmmodding e100 trace calls on 2.6.0-test2-mm2 Peter Johanson
2003-08-01 23:01 ` Stephen Hemminger [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=20030801160149.2392a079.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=latexer@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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;
as well as URLs for NNTP newsgroup(s).