From: Stephen Hemminger <shemminger@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH 2.5.70] Add release_netdev -- hook for sysfs/net device cleanup
Date: Sat, 7 Jun 2003 08:25:15 -0700 [thread overview]
Message-ID: <20030607082515.6168be46.shemminger@osdl.org> (raw)
In-Reply-To: <20030607.020528.68152135.davem@redhat.com>
On Sat, 07 Jun 2003 02:05:28 -0700 (PDT)
"David S. Miller" <davem@redhat.com> wrote:
> From: Stephen Hemminger <shemminger@osdl.org>
> Date: Fri, 6 Jun 2003 14:58:35 -0700
>
> Phase I: introduces release_netdev which is the hook to allow later
> changes to hold onto the net device after the device has potentially
> unloaded. Includes patch for the easy to fix devices.
>
> Besides naming (thought this was going to be named netdev_drop)
> I have no problems.
>
> Al?
My (admittedly weak) rational for this was:
- it seemed more like part of the register/unregister process
and those functions are named {un}register_netdevice
- RTNL should not be held, same as unregister_netdev
(vs unregister_netdevice which requires it).
- release rather than drop because release is used as name
in the kobject callback hook
But it's easy to change now.
next prev parent reply other threads:[~2003-06-07 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 21:58 [PATCH 2.5.70] Add release_netdev -- hook for sysfs/net device cleanup Stephen Hemminger
2003-06-06 23:07 ` Stephen Hemminger
2003-06-07 9:05 ` David S. Miller
2003-06-07 15:25 ` Stephen Hemminger [this message]
2003-06-07 19:15 ` Jeff Garzik
2003-06-08 6:58 ` David S. Miller
2003-06-09 3:51 ` Jeff Garzik
2003-06-09 5:53 ` David S. Miller
2003-06-09 17:09 ` Jeff Garzik
2003-06-09 17:09 ` David S. Miller
2003-06-09 17:14 ` Jeff Garzik
2003-06-09 17:18 ` David S. Miller
2003-06-09 18:11 ` Jeff Garzik
2003-06-07 19:16 ` Jeff Garzik
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=20030607082515.6168be46.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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).