From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: mike.mclagan@linux.org, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [PATCH] dlci - cleanup for 2.6
Date: Wed, 3 Sep 2003 20:33:36 -0700 [thread overview]
Message-ID: <20030903203336.45e0bce6.davem@redhat.com> (raw)
In-Reply-To: <20030903151847.7311f75f.shemminger@osdl.org>
On Wed, 3 Sep 2003 15:18:47 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> Patch for 2.6.0-test4 to cleanup DLCI driver
> - keep list of arrays for devices and use a lock
> - make sure header is contiguous before overlaying data structure
> - dynamically allocate dev->priv with alloc_netdev
> - get rid of MOD_INC/DEC
> - free devices on module unload
> - keep refcount on slave device's since holding a ptr
Applied.
I assume you added the module export of unregister_frad() because you
intend to make some drivers actually make use of it? :-)
parent reply other threads:[~2003-09-04 3:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030903151847.7311f75f.shemminger@osdl.org>]
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=20030903203336.45e0bce6.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=mike.mclagan@linux.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).