From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@redhat.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: Mon, 9 Jun 2003 13:14:46 -0400 [thread overview]
Message-ID: <20030609171446.GA15239@gtf.org> (raw)
In-Reply-To: <20030609.100948.84378474.davem@redhat.com>
On Mon, Jun 09, 2003 at 10:09:48AM -0700, David S. Miller wrote:
> From: Jeff Garzik <jgarzik@pobox.com>
> Date: Mon, 09 Jun 2003 13:09:13 -0400
>
> David S. Miller wrote:
> > That's your plan, but did you do any of this yet? It'll keep
> > going deeper and deeper into bitkeeper history the longer that
> > you wait :-)
>
> Yes, I have been following my plan. You will see when Marcelo opens
> 2.4.22-pre1 that I have been committing these to my net-drivers-2.4 queue.
>
> Awesome.
>
> Now why was I asking this to begin with? You wanted to do something,
> what was that? :-)
I wanted to wait on the s/kfree/release_netdev/ patch until the other
stuff is done. Said patch can be applied anytime, and doing it in this
order reduces 2.4 backport merge pain. :)
Jeff
next prev parent reply other threads:[~2003-06-09 17:14 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
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 [this message]
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=20030609171446.GA15239@gtf.org \
--to=jgarzik@pobox.com \
--cc=davem@redhat.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).