From: Jeff Muizelaar <muizelaar@rogers.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: [PATCH 0/3] NE2000 driver updates
Date: Tue, 01 Apr 2003 13:32:28 -0500 [thread overview]
Message-ID: <3E89DB3C.7020909@rogers.com> (raw)
The first two patches are retransmits of the original PnP api patches
updated to apply to a current tree.
The third patch is more of an RFC. It consolidates the creation/removal
of the driver between the PnP code and the plain ISA code.
In doing so it changes the net_device allocation from static to dynamic
and allows PnP support when the driver is compiled in.
This is probably how things will eventually have to be if there is ever
driver model support for plain ISA devices.
Caveats:
It appears that the patch will break any autoprobe ordering because it
no longer uses Space.c when compiled into the kernel.
Data size of object goes up about 100 bytes.
-Jeff
next reply other threads:[~2003-04-01 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 18:32 Jeff Muizelaar [this message]
2003-04-01 18:33 ` [PATCH 1/3] NE2000 driver updates Jeff Muizelaar
2003-04-01 18:34 ` [PATCH 2/3] " Jeff Muizelaar
2003-04-01 18:35 ` [PATCH 3/3] " Jeff Muizelaar
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=3E89DB3C.7020909@rogers.com \
--to=muizelaar@rogers.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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