netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: jgarzik@pobox.com
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.5.70] Add release_netdev -- hook for sysfs/net device cleanup
Date: Sat, 07 Jun 2003 23:58:25 -0700 (PDT)	[thread overview]
Message-ID: <20030607.235825.71096085.davem@redhat.com> (raw)
In-Reply-To: <20030607191522.GB3346@gtf.org>

   From: Jeff Garzik <jgarzik@pobox.com>
   Date: Sat, 7 Jun 2003 15:15:22 -0400

   I would prefer to fix the drivers _before_ anything else.  i.e. Phase 2
   becomes Phase 1.
   
   These often need to be merged into 2.4 as well, and they can be applied
   to all drivers without any API changes.  The changes are separated out
   from any refcounting/sysfs stuff, and can (potentially) be considered
   and reviewed by the respective maintainers.

Have you extracted out all the init_etherdev() killings Al and
myself did so you can backport them to 2.4.x too?

If you're not going to do that, there is not much point in trying to
sync other such things back to 2.4.x as well.

  reply	other threads:[~2003-06-08  6:58 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
2003-06-07 19:15 ` Jeff Garzik
2003-06-08  6:58   ` David S. Miller [this message]
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=20030607.235825.71096085.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jgarzik@pobox.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).