From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@oss.sgi.com, mochel@osdl.org
Subject: Re: [PATCH] (0/9) free_netdev -- delay freeing of net_device structure till after last use
Date: Tue, 19 Aug 2003 16:13:26 -0400 [thread overview]
Message-ID: <3F4284E6.7070709@pobox.com> (raw)
In-Reply-To: <20030819124818.476dc36d.davem@redhat.com>
David S. Miller wrote:
> Yes, but drivers that want to work with all 2.4.x trees
> will need some kind of define to tip off of. Just providing
> a HAVE_FREE_NETDEV ought to be sufficient.
>
> Jeff?
Yeah, that works for me.
Jeff
next prev parent reply other threads:[~2003-08-19 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 19:18 [PATCH] (0/9) free_netdev -- delay freeing of net_device structure till after last use Stephen Hemminger
2003-08-19 19:48 ` David S. Miller
2003-08-19 20:13 ` Jeff Garzik [this message]
2003-08-19 20:09 ` David S. Miller
2003-08-19 20:28 ` Stephen Hemminger
2003-08-19 20:24 ` Jeff Garzik
2003-08-19 20:24 ` David S. Miller
2003-08-19 20:44 ` Jeff Garzik
2003-08-19 20:30 ` Stephen Hemminger
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=3F4284E6.7070709@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=mochel@osdl.org \
--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).